-
Notifications
You must be signed in to change notification settings - Fork 333
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
Update upload
input values and logic
#1598
Conversation
b6df6de
to
39f1bc6
Compare
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.
Nice!
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.
Some further changelog improvement suggestions!
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.
Very nice!
Previously, failed runs' failed SARIF files were uploaded if the `upload` input was not `true`. Now, the failed SARIF files will be uploaded if the `upload` input was not `always`, `failure-only`, or `true`.
Previously, we uploaded results from the `analyze` step if the `upload` input was `true`. We now upload results if the `upload` input was set to `true` or `always`.
Co-authored-by: Henry Mercer <[email protected]>
Co-authored-by: Henry Mercer <[email protected]>
Co-authored-by: Henry Mercer <[email protected]>
46cf6c6
to
54e08db
Compare
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.
upload
input to theanalyze
Action now accepts the following values:always
is the default value, which uploads the SARIF file to Code Scanning for successful and failed runs.failure-only
is recommended for customers post-processing the SARIF file before uploading it to Code Scanning. This option uploads debugging information to Code Scanning for failed runs to improve the debugging experience.never
avoids uploading the SARIF file to Code Scanning even if the code scanning run fails. This is not recommended for external users since it complicates debugging.true
andfalse
options will be interpreted asalways
andfailure-only
respectively.Merge / deployment checklist