chore: keep CodeRabbit's summary out of the PR description

[nielspardon]

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

Summary by CodeRabbit

• Improvements
  • Code review walkthroughs now include a high-level summary.

[coderabbitai]

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: bf6bf88b-247d-4568-9a47-ad9749f6f5a5

📥 Commits

Reviewing files that changed from the base of the PR and between 046a23c and 600e39c.

📒 Files selected for processing (1)

• .coderabbit.yaml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The CodeRabbit YAML configuration now declares its schema for validation and enables reviews.high_level_summary_in_walkthrough.

Changes

CodeRabbit configuration

Layer / File(s)	Summary
Schema and review setting .coderabbit.yaml	The configuration declares the CodeRabbit schema and sets reviews.high_level_summary_in_walkthrough to true.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 600e3

The high-level summary is configured to appear in the walkthrough instead of the PR description; no actionable merge risk remains.

Architecture Summary

Architecture risk: 🔵 Low · up to 600e3

The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.

Changed systems: None identified.

Architecture concerns
No architecture-level concerns identified.

Review details

Before / after behavior

• observed — Modified behavior in .coderabbit.yaml: Adds the CodeRabbit schema declaration and sets reviews.high_level_summary_in_walkthrough to true.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the change to keep CodeRabbit’s summary out of the PR description.
Description check	✅ Passed	The description explains the rationale, the change, and relevant precedent. It provides the information requested by the template.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

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.}