-
Notifications
You must be signed in to change notification settings - Fork 265
Fix refs used for code scanning results #1346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I'll have to revisit this as apparently just passing the |
aeacaf8
to
849fe0e
Compare
849fe0e
to
155bd70
Compare
sha: ${{ github.event_name == 'workflow_dispatch' && env.CHECKED_OUT_SHA || github.sha }} | ||
|
||
- name: "Upload SARIF report" | ||
if: ${{ github.event_name != 'workflow_dispatch' }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I needed to split this, as the upload-sarif action contains logic to fix the refs/pulls/<number>/merge
ref, but doesn't do so when it was provided explicitly. Thus the only way to retain current logic for pull requests is to invoke the action without ref
and sha
arguments, and then explicitly pass them when the workflow was dispatched manually.
155bd70
to
f7bb2a6
Compare
Note: ignored failing evergreen variants, as they're related to a newer PHPC version. |
There are two changes here:
github.ref
variable is set to the branch that the release workflow was triggered in. This is changed to the tag reference we just created.github.ref
, which was also changed to using the ref of the newly created tag.