Potential fix for code scanning alert no. 7: Workflow does not contain permissions #933
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/equinor/isar/security/code-scanning/7
General approach:
Explicitly add a
permissions
block to the workflow. This can be applied at the top level (affecting all jobs), or per-job (to tailor permissions individually). Since all jobs here automate project and issue/PR management, the minimal required permissions are likelycontents: read
,issues: write
, andpull-requests: write
.Detailed changes:
permissions:
block immediately after thename:
or before theon:
key, or at the start of thejobs:
map.Files/regions/lines to change:
.github/workflows/project_automations.yml
.permissions:
block right after the workflowname:
and beforeon:
to cover all jobs by default.Requirements:
Suggested fixes powered by Copilot Autofix. Review carefully before merging.