Check for $BUILDKITE_PULL_REQUEST = false
when uploading sarif file.
#116
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If build is not associated with a pull request, Buildkite puts value
false
for$BUILDKITE_PULL_REQUEST
Initially, I thought it just doesn't create such variable.
Proof can be found here: https://buildkite.com/automattic/pocket-casts-android/builds/8308#0191e617-a1e2-4ae6-a7bb-4ef3dda51370
Because of this bug, after merge to trunk in Pocket Casts we can see:
CHANGELOG.md
if necessary.