fix: remove pull_request ruleset rule, restore push_allowances - #187
Conversation
|
Warning Review limit reached
Next review available in: 56 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: Repository: osac-project/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
WalkthroughThe changes remove merge-queue-specific pull request enforcement and add explicit push allowances for ChangesRepository access control
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 11✅ Passed checks (11 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 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 |
The pull_request rule in the ruleset blocks PRs when CodeRabbit (or any bot) has an outstanding CHANGES_REQUESTED review — even with required_approving_review_count=0. Since approval is handled by Prow labels and the check-labels gate, not native GitHub reviews, this rule is incompatible. Direct push protection comes from classic branch protection's restrict_pushes (push_allowances) instead. The merge queue bot is auto-allowed by GitHub when restrict_pushes is active, confirmed working in production. Assisted-by: Claude Code <noreply@anthropic.com> Signed-off-by: omer-vishlitzky <omer.vishlitzky@gmail.com>
b9df32d to
73dcb32
Compare
Summary
pull_requestrule from ruleset — it blocks PRs when CodeRabbit has outstanding CHANGES_REQUESTED, even withrequired_approving_review_count=0push_allowancesfor osac and osac-test-infra — classic branch protectionrestrict_pushesblocks direct pushes without interfering with the merge queue bot (confirmed working)Context
The
pull_requestruleset rule enforces native GitHub review requirements. Since OSAC uses Prow labels (lgtm/approved) via thecheck-labelsgate instead of native reviews, this rule is incompatible — CodeRabbit's reviews block merging.Direct push protection via classic branch protection
restrict_pushesworks with the merge queue because GitHub auto-allows the merge queue bot whenrestrict_pushesis active.🤖 Generated with Claude Code
Summary by CodeRabbit