SapMachine #1985: DUMMY DO NOT MERGE

[raeessap]

prevent checks run for forked repo rather fetch results from forked repo (TGSAPJVM-6140)

fixes #1985

[SapMachine]

Hello @raeessap, this pull request fulfills all formal requirements.

[SapMachine]

Hello @raeessap, this pull request fulfills all formal requirements.

[SapMachine]

Thank you for your contribution! 👋

This PR originates from a forked repository. For security reasons, CI builds do not run automatically on fork PRs.

A maintainer will review your changes and trigger the CI by commenting approve testing. If changes are pushed after approval, a new approval will be required.

[raeessap]

approve testing

[raeessap]

approve testing

[SapMachine]

Thank you for your contribution! 👋

This PR originates from a forked repository. For security reasons, CI builds do not run automatically on fork PRs.

A maintainer will review your changes and trigger the CI by commenting approve testing. If changes are pushed after approval, a new approval will be required.

[SapMachine]

Thank you for your contribution! 👋

This PR originates from a forked repository. For security reasons, CI builds do not run automatically on fork PRs.

A maintainer will review your changes and trigger the CI by commenting approve testing. If changes are pushed after approval, a new approval will be required.

[SapMachine]

Thank you for your contribution! 👋

This PR originates from a forked repository. For security reasons, CI builds do not run automatically on fork PRs.

A maintainer will review your changes and trigger the CI by commenting approve testing. If changes are pushed after approval, a new approval will be required.

[SapMachine]

Thank you for your contribution! 👋

This PR originates from a forked repository. For security reasons, CI builds do not run automatically on fork PRs.

A maintainer will review your changes and trigger the CI by commenting approve testing. If changes are pushed after approval, a new approval will be required.