chore: add a .coderabbit.yaml that keeps CodeRabbit's summary out of the PR description - #1343
Conversation
…the PR description CodeRabbit writes its high-level summary into every PR description, which becomes the squash commit message. In a breaking PR the block can land after the BREAKING CHANGE: footer, where semantic-release would publish it as part of the release note; stripTrailers in .releaserc.mjs only removes Key: value trailers and cannot strip it. Move the summary into CodeRabbit's walkthrough comment instead, as substrait-io/substrait#1222 did for the spec repo. Closes substrait-io#1340
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Warning This pull request changes a CodeRabbit configuration file. Because it comes from a fork or its author is not a repository collaborator, reviews use only the configuration from the target branch. The proposed configuration will take effect after it is merged. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review. 📝 WalkthroughWalkthroughThe CodeRabbit configuration now declares the v2 JSON schema and enables high-level summaries in review walkthroughs. ChangesWalkthrough summary configuration
Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other · Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to The summary will appear in the walkthrough rather than the PR description, matching the stated objective; no actionable merge risk remains. Architecture SummaryArchitecture risk: 🔵 Low · up to The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency. Changed systems: None identified. Architecture concerns Review detailsBefore / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
CodeRabbit writes its high-level summary into every PR description, which becomes the squash commit message, so the block ends up in every squash commit unless it is cut out at merge time. In a breaking PR it can also land after the `BREAKING CHANGE:` footer, where semantic-release publishes it as part of the release note. This moves the summary into CodeRabbit's walkthrough comment instead, the same setting substrait-io/substrait#1222 applied to the spec repo and substrait-io/substrait-java#1343 applies there. 🤖 Generated with AI <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Improvements** * Code review walkthroughs now include a high-level summary. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
CodeRabbit writes its high-level summary into every PR description, which becomes the squash commit message, so the block ends up in every squash commit unless it is cut out at merge time. This moves the summary into CodeRabbit's walkthrough comment instead, the same setting substrait-io/substrait#1222 applied to the spec repo and substrait-io/substrait-java#1343 applies there. 🤖 Generated with AI <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated automated review settings to include a high-level summary in review walkthroughs. This change affects how reviews are presented and does not alter product functionality or the end-user experience. No other user-facing changes are included in this update. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
CodeRabbit writes its high-level summary into every PR description, which becomes the squash commit message. In a breaking PR the block can land after the
BREAKING CHANGE:footer, where semantic-release would publish it as part of the release note;stripTrailersin.releaserc.mjsonly removesKey: valuetrailers and cannot strip it.This moves the summary into CodeRabbit's walkthrough comment instead, the same setting substrait-io/substrait#1222 applied to the spec repo.
Closes #1340
🤖 Generated with AI
Summary by CodeRabbit