chore(coderabbit): drop the inert auto_approve block - #36
Conversation
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_51b40a20-3204-46a2-8cff-e9accb0ec40c) |
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 9 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Comment |
ApprovabilityVerdict: Approved af35b05 Removes a non-functional You can customize Macroscope's approvability policy. Learn more. |
auto_approveis not a key in CodeRabbit's live v2 schema (https://storage.googleapis.com/coderabbit_public_assets/schema.v2.json, verified 2026-08-02). The block that occupied this space in.coderabbit.yamlnever did anything, and removing it changes no behaviour.The real control satisfying branch protection is the branch protection rule itself requiring a review — not config in this file. This PR also replaces the surrounding comments, which previously asserted (incorrectly) that this block was what satisfied branch protection, with an accurate note.
Note
Low Risk
Documentation-only cleanup in CodeRabbit config; no application code or CI workflow changes.
Overview
Removes the
auto_approvesection from.coderabbit.yaml(limits on changed files/lines, severity allowlist, and excluded paths for workflows, env files, and wrangler config). That key is not part of CodeRabbit’s v2 schema, so the block had no effect and dropping it does not change review or merge behavior.Comments in the same file are updated to state that branch protection still depends on GitHub’s required-review rule, not this YAML—not on the removed block.
Reviewed by Cursor Bugbot for commit af35b05. Configure here.
Summary by cubic
Removed the inert
auto_approveblock from.coderabbit.yamlsince it isn't in CodeRabbit’s v2 schema; no behavior changes. Updated comments to clarify that branch protection rules (required reviews) are the real control, not this config.Written for commit af35b05. Summary will update on new commits.
Note
Remove inert
auto_approveblock from CodeRabbit configRemoves the
reviews.auto_approvesection from .coderabbit.yaml and replaces it with a comment noting thatauto_approveis not recognized by the current schema.Macroscope summarized af35b05.