ci: declare contents: read workflow permissions - #36
Conversation
CodeQL actions/missing-workflow-permissions flags CI workflows without an explicit permissions block. Match the estate pattern already on agency-automations / creditscan-v2 / ZenSms.
|
Required label not found on this PR. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: ZenSystemAI/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: 5 reviews are currently available. Based on recent review activity, included reviews refill at 6 per hour. 📝 WalkthroughWalkthroughThe CI workflow now grants workflow-level read-only access to repository contents. ChangesCI permissions
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This change limits the workflow token to read-only repository contents and is merge-ready after normal checks and review; no actionable merge-blocking risk remains. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Approved. Cursor Bugbot was not present after the first check poll, so that signal was skipped; the remaining evidence is a least-privilege contents: read addition to .github/workflows/ci.yml with no findings requiring human review. No reviewers were assigned.
Sent by Cursor Approval Agent: Pull Request Router and Approver


Why
CodeQL
actions/missing-workflow-permissionsflags this workflow because it had no explicitpermissions:block, so the default GITHUB_TOKEN was overly broad.Change
Add a top-level least-privilege block:
This matches the estate pattern already on agency-automations / creditscan-v2 / ZenSms.
Scope
.github/workflows/ci.ymlonlySummary by CodeRabbit