Potential fix for code scanning alert no. 10: Workflow does not contain permissions#110
Merged
Potential fix for code scanning alert no. 10: Workflow does not contain permissions#110
Conversation
…in permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
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
1 participant
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/SpringMT/zstd-ruby/security/code-scanning/10
To fix the problem, you should add a
permissionsblock to the workflow to explicitly restrict the permissions granted to the GITHUB_TOKEN. The best way to do this is to add the block at the root level of the workflow file (abovejobs:), so it applies to all jobs unless overridden. For this workflow, which only checks out code and runs tests/benchmarks, the minimal required permission iscontents: read. This change should be made by inserting the following block after thename:field and beforeon::No additional imports, methods, or definitions are required.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.