Test#515
Conversation
CodeRabbit (free for this public repo, configured in .coderabbit.yaml) reviews every pr; the paid claude-code-action is removed. auto-merge no longer runs an ai verify step — the owner arms it (auto-merge label or /auto-merge comment) and a non-core pr merges once ci + trust-gate are green, with codeowners still gating core. drops pr-verify.yml, the pr-verify environment, and the anthropic api key.
chore(pr-bot): swap claude code for coderabbit as the reviewer
make coderabbit a hard merge gate instead of advisory. the new coderabbit-gate workflow reads coderabbit's review verdict via the api and publishes a `coderabbit-approved` commit status, which the branch ruleset now requires — so a labeled non-core pr only auto-merges once coderabbit approves, on top of ci + trust-gate + codeowners. the verdict is scoped to the pr head commit (via each review's commit_id), so a fresh push drops back to pending and cannot ride a stale approval through the gate. a pr coderabbit requests changes on 3 distinct commits without an approval is auto-closed with an explaining comment; the owner and bots are exempt so they can keep iterating. the decision logic (coderabbit_verdict / gate_status / should_close) lives in pr_bot.py as pure stdlib and is covered by tests. the workflow reads only review metadata and checks out the trusted base ref — no untrusted head code runs. org admins keep the ruleset bypass to override the gate when needed.
feat(pr-bot): gate auto-merge on coderabbit approval + 3-strikes close
add a daily scheduled stale-pr-reaper that closes an open pr whose author left CodeRabbit's change request unaddressed — no new commit for 2 days. it complements the 3-strikes close: strikes fires when the author keeps pushing failing commits, this fires when they go silent. the decision (should_close_stale) lives in pr_bot.py as pure stdlib and is scoped to the pr head commit via each review's commit_id, so a push after the review moves head off the reviewed sha and resets the clock. the owner and bots are exempt, matching the strikes exemption. the reaper reads only api metadata and runs from the trusted default branch — no pr head code runs. scheduled workflows only fire from the default branch, so it activates once it reaches main.
feat(pr-bot): auto-close prs stale 2 days after a change request
|
Warning Review limit reached
Next review available in: 48 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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 (10)
✨ Finishing Touches🧪 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 |
github-actions
Bot
added
docs
1 participant
What changed
Why
What might break
VEP
Tests
make checkpasses locally (lint + mypy + pytest)CHANGELOG.mdupdated under## [Unreleased]