Adjust CodeRabbit review config

[ykmr1224]

Description

• Adjust CodeRabbit review config to enable auto review.
• Some more minor changes.

Related Issues

#4889
opensearch-project/.github#412

Check List

• New functionality includes testing.
• New functionality has been documented.
• New functionality has javadoc added.
• New functionality has a user manual doc added.
• New PPL command checklist all confirmed.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff or -s.
• Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Enhanced automated code review configuration to improve review coverage and efficiency with refined review guidelines and streamlined comment behavior.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Walkthrough

The .coderabbit.yaml configuration file was updated to enhance automated review and chat behavior. Changes include enabling high-level summaries in walkthroughs, activating auto-review features, adding path-specific review guidelines, and adjusting chat settings with ASCII art disabled.

Changes

Cohort / File(s)	Summary
Configuration Updates \.coderabbit\.yaml	Enabled auto-review and auto-incremental-review; replaced placeholder with high_level_summary_in_walkthrough flag; enabled collapsed walkthroughs; added path_instructions section with Java, test, PPL, and Calcite-specific review guidelines; extended ignore_title_keywords to include "WIP", "DO NOT MERGE", and "DRAFT"; updated chat settings to disable auto-reply and ASCII art.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Review the new path_instructions section for semantic correctness and coverage of intended file patterns
• Verify keyword expansions in ignore_title_keywords align with desired PR filtering behavior
• Confirm all feature flag enablements (auto_review, auto_incremental_review) are intentional

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change in the PR, which is adjusting the CodeRabbit review configuration file with multiple settings updates.
Description check	✅ Passed	The description is related to the changeset and mentions adjusting CodeRabbit review config to enable auto review, which aligns with the actual changes made to the configuration file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 52fe8aa and 63ac86f.

📒 Files selected for processing (1)

• .coderabbit.yaml (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (27)

• GitHub Check: security-it-linux (21)
• GitHub Check: security-it-linux (25)
• GitHub Check: bwc-tests-full-restart (21)
• GitHub Check: bwc-tests-full-restart (25)
• GitHub Check: build-linux (21, integration)
• GitHub Check: build-linux (25, unit)
• GitHub Check: build-linux (25, doc)
• GitHub Check: build-linux (25, integration)
• GitHub Check: build-linux (21, doc)
• GitHub Check: build-linux (21, unit)
• GitHub Check: bwc-tests-rolling-upgrade (25)
• GitHub Check: bwc-tests-rolling-upgrade (21)
• GitHub Check: build-windows-macos (macos-14, 25, doc)
• GitHub Check: security-it-windows-macos (windows-latest, 21)
• GitHub Check: build-windows-macos (macos-14, 25, unit)
• GitHub Check: build-windows-macos (macos-14, 25, integration)
• GitHub Check: build-windows-macos (macos-14, 21, unit)
• GitHub Check: build-windows-macos (macos-14, 21, doc)
• GitHub Check: build-windows-macos (macos-14, 21, integration)
• GitHub Check: security-it-windows-macos (windows-latest, 25)
• GitHub Check: build-windows-macos (windows-latest, 25, -PbuildPlatform=windows, integration)
• GitHub Check: build-windows-macos (windows-latest, 21, -PbuildPlatform=windows, integration)
• GitHub Check: security-it-windows-macos (macos-14, 25)
• GitHub Check: build-windows-macos (windows-latest, 21, -PbuildPlatform=windows, unit)
• GitHub Check: security-it-windows-macos (macos-14, 21)
• GitHub Check: build-windows-macos (windows-latest, 25, -PbuildPlatform=windows, unit)
• GitHub Check: CodeQL-Scan (java)

🔇 Additional comments (4)

.coderabbit.yaml (4)

13-13: Walkthrough and summary display changes approved.

The enablement of high_level_summary_in_walkthrough and collapse_walkthrough improves readability by placing the high-level summary in the walkthrough and collapsing the output. This is a sensible configuration for automated reviews on an infrastructure project.

Also applies to: 16-16

---

18-25: Auto-review enablement and title keyword filtering look good.

Enabling auto_review with auto_incremental_review: true will trigger automatic reviews on each push. The expanded ignore_title_keywords list (WIP, DO NOT MERGE, DRAFT) appropriately filters review triggering for draft work and non-merge-ready changes.

---

69-70: Chat configuration changes enforce explicit engagement and professionalism.

Setting auto_reply: false requires explicit bot tagging (prevents unsolicited responses) and art: false disables ASCII/Emoji art for more professional communication. These are appropriate for an infrastructure-focused review configuration.

---

28-67: Path patterns are valid and align with OpenSearch SQL project structure.

The path_instructions section adds well-structured, specific review guidelines for five key areas. Verification confirms:

1. Path patterns exist: The repository has confirmed modules including integ-test/ for integration tests, separate ppl/ and Calcite-integrated components. Java source files and test subdirectories follow standard conventions.

2. Guidelines align with OpenSearch SQL practices:

   • **/test/**/*.java and integ-test/**/*IT.java patterns match project conventions (integration tests named with *IT.java suffix, executed via ./gradlew :integ-test:integTest)
   • PPL module separation and Calcite-specific guidance are appropriate given the project's architecture
   • The 20-line method length guideline and naming conventions (PascalCase/camelCase) are standard industry practices

3. Minor note: Ensure team alignment on the 20-line method length threshold and verify any team-specific conventions around Optional usage and try-with-resources patterns, which may vary by project.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}