Potential fix for code scanning alert no. 5: Workflow does not contain permissions #98
Conversation
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
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> Signed-off-by: Dev Mukherjee <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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/anomaly/gallagher/security/code-scanning/5
To fix the problem, add an explicit
permissionsblock to the workflow to limit the permissions granted to the GITHUB_TOKEN. The optimal location in this case is at the workflow root (abovejobs:) if all jobs require the same permissions, otherwise, place it inside individual jobs. Since this workflow is for publishing documentation using GitHub Pages, it typically only needs permission to read and write content within the repository. The minimal safe permissions arecontents: write. If you are certain that only read is needed, you may usecontents: read, but publishing likely requires write access. Therefore, above thejobs:key, insert:No imports or definitions are involved; this is a declarative YAML change.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.