ci: Add permissions to upload security scan results - #51
Open
apyrgio wants to merge 2 commits into
Open
Conversation
Add 'security-events: write' permissions, so that the CI run can upload scan results. This has been documented in the past [1], but it seems it started bitting us today. Note that the 'actions: read' permission does not seem to be required. [1] github/codeql-action#2789 (comment)
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Add 'security-events: write' permissions, so that the CI run can upload scan results. This has been documented in the past 1, but it seems it started bitting us today.
Note that the 'actions: read' permission does not seem to be required.
Footnotes
https://github.com/github/codeql-action/issues/2789#issuecomment-2694501026 ↩