Repository navigation
chore: gate CodeRabbit reviews behind readiness - #1848
juanpflores wants to merge 2 commits into
Conversation
|
@juanpflores is attempting to deploy a commit to the Johannes Stein's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
Updated this PR to use The TypeScript config keeps the existing dynamic |
| auto_review: { | ||
| // This repository opens many small and stacked PRs. Spend a review only | ||
| // when the author marks a coherent change ready for feedback. | ||
| enabled: false, |
There was a problem hiding this comment.
@frostney this is the most abrupt change. Would recommend checking this out before approving. You might be ok already with the incremental reviews being stopped until requested
Summary
review-ready, disable automatic incremental follow-ups, and skipgithub-actions[bot]PRsWhy
This repository opens many small and stacked PRs. The inherited configuration reviews every base branch, while default incremental reviews can spend an included review for every eligible push. In a recent 28-hour period, CodeRabbit posted 81 comments across 40 PRs, including 26 rate-limit notices and 33 notices reporting the reduced 1-review-per-hour allowance.
Making review opt-in keeps CodeRabbit available for coherent, review-ready changes rather than spending allowance on intermediate stack layers, WIP updates, and routine automation. After merging, create the
review-readyGitHub label. Authors can request a later focused pass with@coderabbitai reviewonce they push additional changes.Verification
git diff --check