Repository navigation
ci(coderabbit-config): refresh the vendored CodeRabbit schema - #467
Open
cloud-code-bot[bot] wants to merge 2 commits into
Open
cloud-code-bot[bot] wants to merge 2 commits into
cloud-code-bot[bot] wants to merge 2 commits into
Conversation
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
cloud-code-bot
Bot
force-pushed
the
ci/refresh-coderabbit-schema
branch
from
November 16, 2026 15:05
5592cce to
f25bec9
Compare
…brings The refreshed schema adds `reviews.merge_risk_instructions` and `reviews.security_risk_instructions`, both `maxLength: 3000`, taking the per-field cap set from 15 to 17 (span unchanged at 50 -> 20,000). The vendored-schema census asserted the exact count, so it failed as designed; pin both new caps by value and move the count, and update the two README lines that document it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
ELI5
CodeRabbit changed the published list of rules for its config file. This PR copies the new rules in, so every repo's config check grades against what CodeRabbit actually enforces now. Two newly length-limited settings mean the self-test that counts those limits had to be raised to match.
Upstream's CodeRabbit config schema has drifted from the copy vendored here, which is what
coderabbit-config-validate.ymlgrades every enrolled repo against.maxLengthcaps — may invalidate existing configs (2):reviews.merge_risk_instructions: uncapped → 3000reviews.security_risk_instructions: uncapped → 3000Added properties (3):
reviews.auto_approvals.approve_on_skipped_reviewreviews.merge_risk_instructionsreviews.security_risk_instructionsBefore 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
The invariant unit suite FAILED against the proposed schema as first opened (this run): it pins the exact cap count, which this refresh moves from 15 to 17. That is now addressed in this PR: the census test pins both new caps (
reviews.merge_risk_instructions,reviews.security_risk_instructions, 3000 each) by value and asserts 17, and the two README lines documenting the count say 17. The 50 → 20,000 span is unchanged.Invariant suite output (as first opened)
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:
merge_risk_instructionskey: OK.Deviations: