governance: align review gate with solo-maintainer policy - #32
Conversation
|
Warning Review limit reached
Next review available in: 29 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: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
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 |
Root cause
OriginWeave's local
docs/quality-gates.mdmaderequired independent approvalan unconditional merge gate even when no eligible non-author reviewer path existed. That produced a governance deadlock rather than independent review.Fresh current-repository evidence now proves GitHub itself did not require a counted approving review for the latest protected merge: PR #20 merged to protected
mainat804de47617edc7b045c59f484ba23d823aad7d31after exact-head CI, Security Scan, SAST and review-thread validation with no formal review submission. Separately, issue #26 records that theindependent-reviewersteam route was rejected with HTTP 422 because the team is not a collaborator. Repeating that unchanged route cannot create a valid review.Narrow governance repair
This PR does not weaken technical or security gates. It makes the repository-local review rule satisfiable and explicit:
ON HOLD (solo-maintainer)rather than silently bypassed;TDD lineage
1ec4ec8f97a715ead2610cd4b384514894206347added the governance contract before the quality-gate document satisfied it.133c506094189affd425696ddd8049c90b4d3e9dimplements the minimal policy change.The branch is exactly two paths over protected main:
docs/quality-gates.mdandtests/test_review_governance_contract.py.Partial resolution of #26. Close #26 only after this exact head passes required checks, merges normally, and a subsequent technically clean PR is merge-tested under the reconciled policy.