Upload code scanning results to correct ref when releasing #3006
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.
Same issue as with mongodb/mongo-php-library#1346.
When running the static analysis workflow from the release workflow, the
github.ref
andgithub.sha
point to the release branch instead of the release tag. We have to account for this when uploading the sarif. Usinginputs.ref
works, but thesarif-upload
action also expects asha
input whenref
is given. To account for this, we get the ref forHEAD
onworkflow_dispatch
events so the code scanning results are correctly attached to the release tag.