3f524a2459
The protect-main ruleset requires a check by NAME, and a green check run on a PR head never expires. After the code-health ratchet joined the required set, 32 PRs whose last CI run predated it merged on their old "All required checks pass" green without the ratchet ever running; 20 of them would have been blocked (62 findings, incl. 15 new blind `except Exception`). Renaming the gate to "All required checks pass (v2)" and pointing the ruleset at the new name voids every older green: each open PR needs one fresh CI run, which now includes the ratchet, before it can merge, whoever merges it. The ci.yaml comment documents the bump as the standard step whenever the required set gains a job every PR must pass. live_comment.py keeps both names in its infra list (old runs still render), and a test pins that the gate's current display name never shows as a job.
19 lines
788 B
YAML
19 lines
788 B
YAML
# CodeRabbit configuration.
|
|
#
|
|
# Auto-review is DISABLED repo-wide: the app was enabled at the org level on
|
|
# 2026-08-14 and immediately began reviewing every opened PR. This repo's
|
|
# merge gate is CI ("All required checks pass (v2)") plus maintainer review —
|
|
# CodeRabbit reviews carry no merge weight (protect-main ruleset requires
|
|
# 0 approving reviews), so auto-firing on the full PR firehose adds comment
|
|
# noise without gating value.
|
|
#
|
|
# The bot stays installed and summonable on demand: comment
|
|
# `@coderabbitai review` on any PR to request a one-off review, or
|
|
# `@coderabbitai ignore` to mute it on a PR it has already joined.
|
|
#
|
|
# To re-enable auto-review, flip `enabled: true` below (or delete this file —
|
|
# the app default is on).
|
|
reviews:
|
|
auto_review:
|
|
enabled: false
|