Potential fix for code scanning alert no. 5: Workflow does not contain permissions #1597
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.
Potential fix for https://github.com/github/gh-ost/security/code-scanning/5
To fix the problem, we should explicitly set the
permissionskey in the workflow file.github/workflows/ci.ymlto limit the GITHUB_TOKEN privileges for this workflow/job. The key should be added either at the root level (preferred, as all jobs inherit it unless overridden) or under the specific job (build). Since all steps only read repository contents and upload artifacts (which doesn't require contents write permission), the most restrictive safe starting point iscontents: read. Place thepermissions:block at line 2, directly after thename: CIentry, so that it applies to all jobs unless overwritten.Suggested fixes powered by Copilot Autofix. Review carefully before merging.