ci(issue-lifecycle): allow issues:write in audit workflow contract - #729
Conversation
The full-repo audit comments violations on issues so they are not an unread step summary. This permits issues:write in the issue-lifecycle.yml contract while keeping contents and pull-requests read-only. Applied separately from the workflow change so the proposed-workflow check can validate the new workflow against the updated contract.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
Next review available in: 46 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe workflow permission assertion now allows ChangesIssue lifecycle permissions
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/scripts/test-issue-lifecycle-workflow.rb:
- Around line 15-19: Update the expected permissions assertion in the lifecycle
workflow test to match the workflow’s currently declared permissions,
specifically the issues permission, unless the workflow is updated in the same
change to grant issues write access. Keep the assertion aligned with the actual
minimal permissions configuration so the focused validation passes.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: dec6e62f-debd-45d5-92c3-c7c8075a81b6
📒 Files selected for processing (1)
.github/scripts/test-issue-lifecycle-workflow.rb
Address CodeRabbit review: the assertion must stay aligned with the workflow's actually-declared permissions. Accept issues: read (historical read-only audit) or issues: write (full-repo audit comments violations on issues), while contents and pull-requests remain strictly read-only.
Change contract
Permit
issues: writein the issue-lifecycle audit workflow contract, so thefull-repo audit can comment violations on issues instead of leaving them as an
unread step summary.
contentsandpull-requestsstay read-only.This change is deliberately scoped to the contract test only (workflow file is
not touched), so the
Verify proposed workflow contractstep can validate thefollow-up workflow change against this updated contract once both merge.
Issue relationship
None
Out of scope
The actual
issue-lifecycle.ymlworkflow change (addingissues: writeandthe comment step) is a separate follow-up PR so the proposed-workflow check can
validate it against this updated contract.
Dependencies and merge order
None (must merge before the follow-up workflow change).
Focused validation
ruby .github/scripts/test-issue-lifecycle-workflow.rbpasses against theupdated contract
Rollout and rollback
None (CI contract only). Rollback is reverting this PR.
Scope exception
None (1 file).
Summary by CodeRabbit