Potential fix for code scanning alert no. 1: Workflow does not contain permissions#860
Merged
Potential fix for code scanning alert no. 1: Workflow does not contain permissions#860
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
rhernandez35
approved these changes
Aug 27, 2025
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.
Potential fix for https://github.com/smithy-lang/smithy-java/security/code-scanning/1
To resolve the issue, add a
permissionsblock with the minimum required privileges for the workflow. The best way to fix this is to addpermissions: { contents: read }at the top level of the workflow (just after thename:line), which will apply to all jobs in the workflow except those with an override. This change preserves existing functionality while explicitly limiting the GITHUB_TOKEN's access. If the action needs to open pull requests, the minimal required write permission for that purpose (e.g.,pull-requests: writeorcontents: write) should also be added, but with the information provided, start withcontents: readas suggested by CodeQL.Suggested fixes powered by Copilot Autofix. Review carefully before merging.