Skip to main content
Maintain CodeRabbit configuration for your entire organization in one dedicated repository. Create a coderabbit repository in your organization and add your .coderabbit.yaml file - CodeRabbit automatically applies these settings to any repository that doesn’t have its own configuration.

Organization-wide consistency

Single source of truth for code review standards across all repositories

Simplified management

Update settings once instead of modifying each repository individually

Configuration hierarchy

Global overrides take precedence over everything, followed by repository configs, central configs, and organization defaults - giving admins enforcement power while keeping teams flexible

​
How configuration resolution works

CodeRabbit checks for configuration in this priority order:
PrioritySourceLocation
0 (Highest)Global overridesCodeRabbit UI - Organization Settings - Global Overrides
1Repository file.coderabbit.yaml in the repository
2Central repository.coderabbit.yaml in coderabbit repository
3Repository settingsCodeRabbit UI - Repository Settings
4Organization settingsCodeRabbit UI - Organization Settings
5 (Lowest)Default settingsCodeRabbit schema defaults
Global overrides are applied as the final layer, after all other sources (including the inheritance chain) have been resolved. This makes them the authoritative source of truth - any value set in global overrides wins over every other configuration layer. The configuration source appears in the CodeRabbit comment on the pull request:
  • Repository file: Path: .coderabbit.yaml
  • Central repository: Repository: coderabbit/.coderabbit.yaml
  • UI settings: CodeRabbit UI
For enforcing organization-wide policies that repositories cannot override, see Global overrides.

​
Setup

Critical requirement: You must install CodeRabbit on the central coderabbit repository. CodeRabbit needs access to read the configuration file.
1

Create the central repository

Create a repository named coderabbit in your organization. The location depends on your platform:
  • GitHub: organization/coderabbit
  • GitLab: group/coderabbit (or group/subgroup/coderabbit for nested groups)
  • Azure DevOps: project/coderabbit
  • Bitbucket Cloud: workspace/coderabbit
2

Add your configuration

Create a .coderabbit.yaml file in the repository root with your organization’s settings:
# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
reviews:
  in_progress_fortune: false
  profile: chill
  request_changes_workflow: true
  high_level_summary: true
  poem: false
  review_status: true
  auto_review:
    enabled: true
    drafts: true
chat:
  art: false
3

Install CodeRabbit

Install CodeRabbit on the central coderabbit repository through your platform’s installation process.
4

Verify configuration

Check a repository that doesn’t have its own .coderabbit.yaml file. The configuration source should show Repository: coderabbit/.coderabbit.yaml in the CodeRabbit UI.

​
GitLab hierarchical configuration

GitLab supports team-specific configurations through its nested group structure. CodeRabbit automatically finds the closest coderabbit repository in your group hierarchy, allowing different teams to have their own settings while maintaining organization-wide defaults. Configuration inheritance example:
Project pathConfiguration used
company/team-a/subteam/project1company/team-a/subteam/coderabbit
company/team-a/project2company/team-a/coderabbit
company/team-b/project3company/coderabbit
This enables team-specific configurations with automatic fallback to parent group settings.
For configuration inheritance to work across the group hierarchy, CodeRabbit must be installed on the top-level group (for example, company in the table above). This grants CodeRabbit the access it needs to discover and read coderabbit repositories at every level of the hierarchy.

​
Platform limitations

  • Azure DevOps: Each project requires its own coderabbit repository - no cross-project configuration sharing
  • Bitbucket Server: Central configuration not yet implemented - use individual repository settings

​
Repository overrides

Individual repositories can override central configuration by adding their own .coderabbit.yaml file. 
# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
# Repository-specific config
reviews:
  profile: assertive
  high_level_summary: true
  poem: true
  review_status: true
  auto_review:
    enabled: true
    drafts: false
chat:
  art: true
When a repository has its own configuration file, CodeRabbit uses that instead of the central configuration. Repository settings take precedence over central settings.