Potential fix for code scanning alert no. 8: Workflow does not contain permissions#352
Draft
Potential fix for code scanning alert no. 8: Workflow does not contain permissions#352
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> Signed-off-by: Håkan Ströberg <hakan.stroberg@codeware.se>
|
|
|
View your CI Pipeline Execution ↗ for commit a0e0d43
☁️ Nx Cloud last updated this comment at |
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
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/codeware-sthlm/codeware/security/code-scanning/8
To resolve the issue, add an explicit
permissionsblock to the workflow file. Place this block at the top workflow level (aftername:andon:), so it applies to all jobs by default. Since the jobs only require access to check out the source code and upload/download artifacts (which do not require write access to the repository), the minimum required iscontents: read. If none of the jobs requirewriteaccess to issues, pull-requests, or other resources, there is no need to add further permissions. If future jobs need broader access, their permissions can be overridden at the job level.Steps:
permissions:section after theon:block (beforeenv:or any other top-level keys).contents: read.Suggested fixes powered by Copilot Autofix. Review carefully before merging.