Conversation
drafts was explicitly set to true (the opposite of CodeRabbit's default false), so draft PRs burned review budget before they were even ready. Reverted to false. auto_pause_after_reviewed_commits defaults to 5. This repo's PRs commonly get several small fast-follow commits pushed within one session (fmt/ clippy fixes, review-response commits) which each count toward the same per-developer review-rate limit as a fresh PR. Lowered to 2 so incremental auto-review pauses earlier on active branches; a fresh pass is still one `@coderabbitai review` comment away when actually wanted. Also added ignore_title_keywords (WIP/DO NOT MERGE/[skip review]) and ignore_usernames for common bot accounts, both no-cost exclusions that don't affect real PRs. Agentflare-Agent: claude-code_2-1-217_agent Agentflare-Branch: task/315 Agentflare-Item: 315
|
Warning Ignoring CodeRabbit configuration file changes. For security, only the configuration from the base branch is applied for open source repositories. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe auto-review configuration now skips draft pull requests, pauses after two reviewed commits, and excludes pull requests matching specified title keywords or automation usernames. ChangesAuto-review configuration
Estimated code review effort: 1 (Trivial) | ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 Checkov (3.3.8).coderabbit.yamlTraceback (most recent call last): 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 |
Summary
Repeated "CodeRabbit: Review rate limited" seen this session on PR #306 and #308. Current
.coderabbit.yamlonly setdrafts: true— the opposite of CodeRabbit's own default (false), so draft PRs were burning review budget too.Per CodeRabbit's own auto-review docs (
docs.coderabbit.ai/configuration/auto-review), the highest-leverage lever for our specific pattern (small PRs, several fast-follow commits pushed within one session — fmt/clippy fixes, review-response commits) isauto_pause_after_reviewed_commits, which defaults to 5 and counts every incremental auto-review toward the same per-developer rate limit as a fresh PR review.Changes
drafts: false— reverted to CodeRabbit's default; draft PRs no longer auto-reviewed.auto_pause_after_reviewed_commits: 2— pauses incremental auto-review after 2 reviewed commits on an active branch instead of 5. A fresh pass is still one@coderabbitai reviewcomment away when actually wanted.ignore_title_keywords: ["WIP", "DO NOT MERGE", "[skip review]"]— no-cost opt-out for PRs explicitly marked not-ready.ignore_usernamesfordependabot[bot]/renovate[bot]/github-actions[bot]— no-cost, doesn't affect any real PR in this repo today.Deliberately did not go all the way to
enabled: false+ label-based opt-in — that fits teams where most PRs don't want review by default; this repo's PRs are almost all real, mergeable work that should keep getting reviewed automatically. The chosen levers target the actual observed pattern (rate limit hit on active branches with repeated small pushes) without adding a manual labeling step to every PR.Test plan
yaml.safe_load)Summary by CodeRabbit