Skip to main content
You can set review behavior once and apply it to every repository in your organization. Each approach below differs in whether repositories can change the values, whether the values live in Git, and which platforms support it.

Before you start

Choose an approach

Use Organization defaults when admins manage the baseline in the web app. Use central configuration when the baseline should be reviewed and versioned like code, or when you’re on self-hosted CodeRabbit. Use workspace settings when several organizations in one workspace share a baseline. Use global overrides only for the few values teams must not change. A shared remote file suits a group of repositories that shares one file without a central repository for the whole organization.

Set Organization defaults

Organization defaults apply to every repository whose Use organization settings toggle is on, which is the default. A repository file or a central file takes priority over them.
  1. Open Review > Review settings.
  2. In Select repositories, select the Organization defaults row.
  3. Change settings in the form, or set View mode to YAML editor.
  4. Select Apply changes, then Apply changes again in the confirmation dialog.
See Settings in the web app.

Set up central configuration

  1. Create a repository named coderabbit in your organization.
  2. Add .coderabbit.yaml or .coderabbit.config.ts at its root.
  3. Install CodeRabbit on the repository.
  4. Open a pull request in a repository that has no file of its own and run @coderabbitai configuration. Values from the file show Central YAML.
Central configuration applies to repositories without their own file. See Central configuration for how each Git platform finds the repository.

Let repositories customize with inheritance

Add inheritance: true to a repository file so it keeps the central values it doesn’t set. Without it, the repository’s omitted keys resolve to schema defaults.
.coderabbit.yaml in the coderabbit repository

Use workspace settings

Enterprise customers with an SSO workspace can set a shared baseline for every organization in it. A workspace admin turns on Use workspace settings as defaults on Workspace management > General. Workspace settings then fill only the keys that no other layer sets. See Workspace settings.

Enforce values instead

Use global overrides for values that no repository may change. Don’t use them as general defaults.

Share one file across repositories

A repository file that contains only remote_config is replaced by the file it points to. CodeRabbit follows the pointer once. Prefer central configuration for many repositories, and point remote_config at a repository rather than a URL, because repository sharing is more secure. See Configuration file. A TypeScript configuration can’t use remote_config. It uses includeRemote to pull a shared fragment and combine it with its own settings in code. See Share TypeScript fragments.

Change many repositories in the web app

  1. In Select repositories, check each repository, or All.
  2. Select the Edit button below the list.
  3. Change settings and apply them.
Saving in the multi-repository editor turns off Use organization settings in each repository that has changes. Every saved value, including fields you didn’t edit, then replaces Organization defaults there. A repository file and global overrides still outrank them.

Check the result

Open a pull request in a repository without its own file and post @coderabbitai configuration. Each value’s # Source: comment names the layer that applies. See Check which configuration a review used.

What’s next

Enforce settings teams can't change

Pin values with global overrides and lock the configuration branch.

Inheritance and merging

See how CodeRabbit combines layers, lists, and nested values.

Central configuration

Set up the coderabbit repository on your Git platform.