chore(ci): least-privilege workflow permissions - #31
Conversation
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_2f868702-0895-4d87-bda2-a5f2692cc91e) |
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 53 minutes Limit details: You’ve used all 1 included review currently available under your plan. You completed 103 included PR reviews in the past 7 days; at that activity level, included reviews refill at 1 review per hour. Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Warning Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption. Comment |
Code Review ✅ ApprovedAdds top-level read-only permissions to the CI test workflow to resolve CodeQL missing workflow permissions findings. No issues found. OptionsAuto-apply is off → Gitar will not commit updates to this branch. Comment with these commands to change the behavior for this request:
Was this helpful? React with 👍 / 👎 | Gitar |
There was a problem hiding this comment.
Risk: medium. Left a non-blocking comment and did not approve because Cursor Bugbot skipped (usage limit) rather than completing successfully; Cursor Security Agent passed with no findings. Human review is needed; no eligible non-author reviewers were available to assign.
Sent by Cursor Approval Agent: Pull Request Router and Approver
ApprovabilityVerdict: Approved 66bdc94 This PR adds explicit least-privilege permissions to a CI workflow, a standard security hardening practice. The change is minimal, doesn't affect runtime behavior, and the author owns the workflow file. You can customize Macroscope's approvability policy. Learn more. |
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can route each action level your way: inline, summary, both, or drop |
Qodo FixerNo findings are available for this PR yet. Findings appear here once Qodo has reviewed the PR. |


Fixes CodeQL
actions/missing-workflow-permissions.Adds top-level
permissions: contents: readto read-only CI/check workflows (no deploy, no release, no reusable write-workflow call). No workflow logic or triggers changed.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Note
Cursor Bugbot is generating a summary for commit 66bdc94. Configure here.