Configuration Inheritance (Merging) for Central Configuration

[hybrid berry]

Hi Team, I'm currently using CodeRabbit on the Pro Plan.

I recently started exploring the Central Configuration feature by adding a coderabbit repository to our GitHub Organization. I noticed that if a target repository has its own .coderabbit.yaml, it completely replaces the central configuration.

Request:
It would be extremely helpful if we could have a "merge" strategy (or configuration inheritance). Ideally, I’d like to define a "base" configuration at the Organization level (e.g., language settings, tone) and allow individual repositories to only partially override specific sections or rules, rather than replacing the entire file.

Use Case:
We manage over 100 repositories across 10+ teams. Allowing local repos to inherit global defaults while customizing only what's necessary would significantly streamline our operations. Currently, maintaining full config files for every repo just to change one small setting is quite difficult.

[errant dawn]

I agree that is really missing. I was asking about few months ago and we received this https://docs.coderabbit.ai/configuration/central-configuration. However, merging configs would be much better when you have so many repositories.

[polar smelt]

The lack of this feature is quite frustrating. I'm also confused because the initial documentation for this feature said that merging works. It seems they have walked that back.

Old screenshot:

[polar smelt]

@hybrid berry @errant dawn I am happy to report that CodeRabbit has recently added configuration inheritance (when it's explicitly enabled):

• https://docs.coderabbit.ai/changelog#configuration-inheritance

[errant dawn]

this is amazing! thank you!

[hybrid berry]

Wow! Thanks for the quick update!

[errant dawn]

I wish the CodeRabbit team had been more responsive and communicated what they are working on. It would improve the UX a lot, knowing that they're working on some features 😉 Recently I have a feeling that this Discord channel is for customers of Coderabbit and not for communications between customers and the CodeRabbit team 😄