Potential fix for code scanning alert no. 5: Workflow does not contain permissions#20
Merged
Potential fix for code scanning alert no. 5: Workflow does not contain permissions#20
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> Signed-off-by: Nathaniel Starkman <nstarman@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/GalacticDynamics/plotting_backends/security/code-scanning/5
To resolve this, you should add an explicit
permissionsblock to either the root of the workflow (to apply to all jobs), or to each job (for finer granularity). The minimal sufficient permission for these jobs are likely to be only read access to repository contents:contents: read. No steps shown require writing to the repository, interacting with issues or pull requests, or other elevated actions, so write access does not need to be granted. The change should be made near the top of the workflow file (e.g., after thename:and beforeon:) for all jobs, or directly underneath the specific job(s) if only certain jobs need reduced permissions.Suggested fixes powered by Copilot Autofix. Review carefully before merging.