chore: fix coderabbit config

[ymc9]

Summary by CodeRabbit

• Chores
  • Refined automated review settings by relocating the base-branch configuration under auto-review to ensure consistent behavior across pull requests and improve review pipeline stability.
  • Internal maintenance only: no changes to features, UI, or performance for end-users.
  • Deployment and usage remain unchanged.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Moved the YAML key path for base branches from reviews.base_branches to reviews.auto_review.base_branches within .coderabbit.yaml. No other files or public interfaces were changed.

Changes

Cohort / File(s)	Summary
Config ./.coderabbit.yaml	Relocated YAML key: reviews.base_branches -> reviews.auto_review.base_branches; no other content changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

I twitch my whiskers at indents slight,
A branch now nests in auto’s light.
Hop-hop through YAML fields I roam,
One step deeper—now it’s home.
Carrot emojis queued to cheer 🥕,
Config snug, the path is clear!

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between e23453d and eba2cad.

📒 Files selected for processing (1)

• .coderabbit.yaml (1 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/coderabbit-config

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[claude]

Claude finished @ymc9's task —— View job

---

Pull Request Review

Todo List

• Read the modified .coderabbit.yaml file
• Check git diff to see exact changes
• Analyze configuration changes for correctness
• Provide comprehensive review feedback

Review Summary

This is a simple but important indentation fix for the CodeRabbit configuration file.

Analysis

Change Made:

• Fixed indentation of base_branches: ['dev', 'main'] on line 7
• Moved from being a top-level property under reviews to being properly nested under auto_review

Before:

reviews:
    auto_review:
        enabled: true
    base_branches: ['dev', 'main']  # Wrong indentation

After:

reviews:
    auto_review:
        enabled: true
        base_branches: ['dev', 'main']  # Correct indentation

Code Quality Assessment

✅ Configuration Correctness: The fix is correct. The base_branches property should be nested under auto_review according to CodeRabbit's schema.

✅ Best Practices: Proper YAML indentation and structure alignment with the schema.

✅ No Security Concerns: This is a configuration file with no security implications.

✅ No Performance Impact: Configuration change only affects CodeRabbit's behavior, no runtime performance impact.

Recommendation

LGTM - This is a necessary fix that ensures CodeRabbit will properly respect the base branch configuration for automatic reviews. The change aligns with CodeRabbit's expected schema structure.

The fix ensures that automatic reviews will only trigger for PRs targeting the dev and main branches as intended.

---