chore: disable CodeRabbit auto-incremental-review to reduce credit burn - #80
Conversation
CodeRabbit's default auto_incremental_review re-reviews on every push. This workstream pushes several fix commits per PR (a normal iteration pattern), and each push was silently spending a review credit whether or not a fresh review was actually wanted yet. On the Pro Plus plan's 7-day fair-use throttle, this was enough activity to drop per-developer availability to "1 review/hour, one at a time" -- confirmed via the non-consuming `@coderabbitai rate limit` check, not a free-tier/plan misconfiguration. Keeps the automatic review CodeRabbit already does when a PR first opens, but stops it from auto-reviewing every subsequent push. Fix-commit batches now get reviewed deliberately via `@coderabbitai review`/`full review` once a PR is actually ready to be looked at again. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 53 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. ✨ 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 |
1 participant
Summary
User asked to investigate why CodeRabbit reviews kept getting rate-limited and whether an account setting needed to change. Findings:
@coderabbitai rate limitcommand → "more reviews will be available in 56 minutes," matching that bracket.auto_incremental_review: truere-reviews on every push, not just once. This workstream pushes several fix commits per PR (normal iteration), and each push was silently spending a review credit — e.g. PR feat(runtime): real load-time VRAM measurement from llama.cpp log lines #77 alone generated 4 separate CodeRabbit comment events across 3 pushes plus 2 manual triggers.Change
Adds
.coderabbit.yamlwithauto_incremental_review: false. Keeps CodeRabbit's automatic review when a PR first opens, but stops it from auto-reviewing every subsequent push. Fix-commit batches get reviewed deliberately via@coderabbitai review/full reviewonce a PR is actually ready to be looked at again, instead of on every intermediate commit.Not done (billing decision, not mine to make)
CodeRabbit also offers a paid usage-based add-on ($0.25/file) to bypass the fair-use throttle entirely — left entirely to the user's discretion, not enabled.
Caveat
Per CodeRabbit's docs, config is read from "the feature branch under review" — it's not fully certain this retroactively changes behavior on PR #77/#78/#79 (opened before this file existed) without those branches picking it up too. It will apply cleanly to all new PRs branched from master after this merges.
🤖 Generated with Claude Code