ci: add explicit permissions to workflow jobs#2388
Conversation
a2984c1 to
2d74cb8
Compare
|
Assessment: Approve Clean and well-scoped security hardening PR. The workflow permission declarations follow the principle of least privilege correctly ( Review Notes
Straightforward security improvement — LGTM. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Documentation Preview ReadyYour documentation preview has been successfully deployed! Preview URL: https://d3ehv1nix5p99z.cloudfront.net/pr-cms-2388/docs/user-guide/quickstart/overview/ Updated at: 2026-06-05T20:11:17.400Z |
2d74cb8 to
dbd2952
Compare
- Add permissions: {} to ci-gate job (needs no token access)
- Add permissions: contents: read, issues: write to
check-links job (reads repo, may create issues)
dbd2952 to
831bd02
Compare
831bd02 to
6a7faed
Compare
|
Assessment: Approve Clean security-hardening PR. The workflow permission additions follow the principle of least privilege correctly, and the lock file regenerations resolve documented transitive dependency vulnerabilities. Review Notes
|
|
Assessment: Approve Straightforward security hardening — both permission declarations are minimal and correct for their respective jobs. Verification
|
| @@ -8,6 +8,9 @@ on: | |||
| jobs: | |||
| check-links: | |||
There was a problem hiding this comment.
Does this actually work? I didn't even know this was a workflow we maintained
Summary
permissions: {}toci-gatejob inci.yml(uses no token, so empty permissions is correct)permissions: { contents: read, issues: write }tocheck-linksjob inpython-check-markdown-links.ymlTest plan