Potential fix for code scanning alert no. 2: Workflow does not contain permissions#33
Merged
AlexGalichenko merged 1 commit intomainfrom Nov 4, 2025
Merged
Potential fix for code scanning alert no. 2: Workflow does not contain permissions#33AlexGalichenko merged 1 commit intomainfrom
AlexGalichenko merged 1 commit intomainfrom
Conversation
…n 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/qavajs/steps-memory/security/code-scanning/2
To fix the problem, add a
permissionsblock at the top level of the workflow, just after thenamekey. This ensures all jobs in the workflow inherit the specified minimal permissions for the GITHUB_TOKEN, promoting the principle of least privilege. As a minimal starting point (and since the job appears to only build and test code, not write to the repository or open issues, etc.), set:If the workflow later requires more privileges (such as writing pull request comments), this block can be extended. No other code changes, imports, or definitions are required—just insert the
permissionsblock in.github/workflows/pull-request.ymlafter thenamekey.Suggested fixes powered by Copilot Autofix. Review carefully before merging.