chore(coderabbit): pause automatic reviews after two reviewed commits

[bompus]

.coderabbit.yaml sets reviews.auto_review.auto_pause_after_reviewed_commits to 0. In CodeRabbit's configuration reference that value turns the pause off, so every push to a pull request is reviewed again. This changes it to 2: automatic review stops after two reviewed commits, which caps re-reviews of a pull request that keeps getting fixup pushes. CodeRabbit's default is 5.

Why 2: across a week of pull requests in several repositories, about 70% of CodeRabbit's reviews were re-reviews of a later push, and a cap of two would have cut the review count by roughly 44%. That is an estimate from review counts. The counts do not time each finding to the review that raised it, so I cannot say how many findings the cap would have removed. 30 of the 36 major findings were on pull requests that got more than two reviews, so the cap can lose some late findings in exchange for fewer reviews and fewer rate-limit stalls.

Checks I ran:

• Key and type confirmed against the CodeRabbit configuration reference and the published schema (https://coderabbit.ai/integrations/schema.v2.json): integer, default 5, minimum 0, "Set to 0 to disable".
• .coderabbit.yaml validates against that schema with 0 errors after the change; a string value in the same place gives 1 error, so the check does reject bad values.
• npx --yes oxfmt@0.70.0 --check . exit 0; npx --yes oxlint@1.85.0 . exit 0; node --test test/*.test.mjs exit 0.

Not known: the docs do not say how a paused review shows in the pull request status or how to resume it. I will look at the first pull request that pauses and record what it shows.

Not changed: no other .coderabbit.yaml key, and CodeRabbit stays on. No CHANGELOG.md entry, because this configures the repository's own review bot and nothing in the npm package changes.

• The checks in the README's Development section pass (formatter, linter and Node tests; check:package and bun test not run, no packaged or tested file changed).
• A change users will notice has a CHANGELOG.md entry under Unreleased (none needed, see above).
• Nothing names a private project or repository, a local path, a home directory or a credential.

---

Summary by cubic

Pauses CodeRabbit's automatic review after two reviewed commits per pull request, so fixup pushes after that no longer trigger a new review. The previous value of 0 disabled the pause, which meant every push was reviewed again; CodeRabbit's default is 5.

Trade-offs

• A cap of two is estimated to cut re-reviews by roughly 44% based on a week of pull requests across several repositories, trading away findings that only surface after the second push, which are more common on larger pull requests.
• The file validates against CodeRabbit's published schema, and the formatter, linter, and Node tests pass.

^{Written for commit 8fd550a. Summary will update on new commits.}

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Configuration used: Repository YAML (base), Organization UI (inherited)
• Review profile: CHILL
• Plan: Advanced
• Run ID: 35ce7d6e-21cc-46ac-a031-4c1fa0315e4c

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}