Repository navigation
ci(coderabbit-config): refresh the vendored CodeRabbit schema - #336
Merged
Merged
Conversation
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
cloud-code-bot
Bot
force-pushed
the
ci/refresh-coderabbit-schema
branch
from
September 28, 2026 15:09
b0342e3 to
12ac5dd
Compare
cloud-code-bot
Bot
force-pushed
the
ci/refresh-coderabbit-schema
branch
from
October 5, 2026 15:09
50685be to
b3b0037
Compare
…copy The two census assertions have been red on main since #250, not since this refresh. #250 vendored the `vale` tool object (omitted 104 -> 105) and #288 added `chat.integrations.jira.issue_template` (caps 14 -> 15); neither updated the tests that pin those counts. Both counts are identical on main and on this branch, so this refresh did not move either one -- it only inherited the red. Its own additions, `reviews.allow_author_approval` and `reviews.tools.ast-grep.enabled`, are leaves and change no census. Both deltas are genuine upstream growth rather than a regression, so the counts move deliberately -- refresh-coderabbit-schema.yml asks the refresh PR to do exactly this -- and the assertions are tightened rather than merely bumped: the 15th cap's value is pinned so it is checked and not just counted, and the 50 -> 20,000 span README documents is now asserted outright. `explicit` still holds at 5, so the refresh introduced no new opener keyword and the openness walk still means what its docstring claims. README's "14 per-field caps" follows the schema in the same commit, per the rule that deleting or changing a documented fact is a docs change too. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mattmillerai
approved these changes
Oct 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upstream's CodeRabbit config schema has drifted from the copy vendored here, which is what
coderabbit-config-validate.ymlgrades every enrolled repo against.Added properties (2):
reviews.allow_author_approvalreviews.tools.ast-grep.enabledBefore merging, check the tightened-cap section above if there is one: a lowered
maxLengthretroactively invalidates configs nobody has touched, and merging this makes their next PR red. Landing the cleanup alongside is usually the right order.Note
Census assertions re-synced in b22252d. The two failures below were inherited from main (red since #250 / #288, identical counts on main and on this branch), not caused by this refresh: its two added properties are leaves. b22252d moves
omitted104 → 105 andcaps14 → 15 deliberately, pins the 15th cap's value (chat.integrations.jira.issue_template= 3000) and the documented 50 → 20,000 span, and updates README's cap count. The output below is the refresher's original run, kept for the record.Warning
The invariant unit suite FAILS against the proposed schema (this run). That suite asserts the exact facts the checker's messages rest on, so this is the signal to read closely, not a flake: either the schema change is one we must adapt the checker and its tests to, or the fetch is not what we think it is. Update those assertions in this PR, deliberately, before merging.
Invariant suite output
Merging this touches
.github/coderabbit-config/**, which triggersbump-coderabbit-config-callers.ymland rolls the SHA-pinned caller fleet forward.Opened by the
refresh-coderabbit-schemaworkflow.Provenance
Verified:
python3 -m unittest discover -s .github/coderabbit-config/tests -p 'test_*.py'— 99 tests OK on b22252d (2 census failures on b3b0037 and on main);check_agents_md.py --root .andcheck-org-repo-literals.shpass.Deviations: Test and README census updates added on top of the refresher's commit; the schema itself is unchanged from the refresh.