Repository navigation
Conversation
The repository's default workflow token permission is write, and these twelve workflows set no permissions of their own, so every job was handed a token able to write to the repository. None of them use it for anything beyond checking out the code and uploading artefacts, so restrict the token to contents: read, matching the workflows that already declare it. This clears the CodeQL actions/missing-workflow-permissions alerts.
|
No actionable comments were generated in the recent review. WalkthroughTwelve GitHub Actions workflows now declare ChangesCI workflow permissions
Estimated code review effort: 2 (Simple) | ~8 minutes Change: Other Possibly related PRs
Suggested reviewers: Merge Risk:
|
|
Merged as ea1a1db. |
The repository's default workflow token permission is write, and twelve of the check and test workflows declare no
permissions:of their own, so their jobs get a write token they never use. This adds a top-levelpermissions: contents: readto each, matchingacceptance-test.ymlandsnapshot.yml, and clears the 12 CodeQLactions/missing-workflow-permissionsalerts.None of the affected jobs use the token beyond
actions/checkoutandactions/upload-artifact. I've checked that this merges cleanly with #10727 in either order, and its newcheck-epas-secretsjob is fine with read-only permissions.Summary by CodeRabbit