Skip to main content
When a setting doesn’t apply, another layer usually supplies the value, or CodeRabbit read a different file than you expected. Find which one, then use the matching fix below.

Before you start

Find which layer supplied the value

  1. Post @coderabbitai configuration as a comment on a pull request. See Check which configuration a review used.
  2. Find your setting in the YAML and read its # Source: comment.
  3. Open the accordion below that matches the label or the symptom.

Match the symptom

Cause. The file isn’t on the branch CodeRabbit reads. In Auto, CodeRabbit reads the pull request branch only for a trusted pull request: same repository, not a fork, and an author who meets your Git provider’s trust rule. Fork pull requests and other authors use the configuration at the pull request’s base commit. Events that aren’t pull requests read the default branch. On GitHub Cloud, a saved Configuration source of Default branch or Custom changes the branch.Fix. Commit the file on the branch CodeRabbit reads. Check Run configuration in Review info to see the branch it read. A saved source that becomes unavailable falls back to Auto with a warning. See Choose the configuration branch.
Cause. CodeRabbit uses one repository file: the first that exists of .coderabbit.yaml, .coderabbit.yml and .coderabbit.config.ts. A YAML file wins over the TypeScript file, and the files are never merged. The same rule applies in the central repository.Fix. Delete the YAML file to activate the TypeScript configuration, then check the result. See TypeScript configuration.
Cause. A repository file doesn’t fall back to central or web interface values for keys it omits unless inheritance is on. Omitted keys resolve to schema defaults. For example, a timeout set in Organization defaults and in central configuration is ignored when the repository file omits it and inheritance is off.Fix. Add inheritance: true to the repository file, or set the key in the file. See Inheritance and merging. Global overrides and Use workspace settings as defaults apply even without inheritance.
Cause. Two layers can outrank them.
  • A central configuration file applies before Repository settings. CodeRabbit reads Repository settings only when no valid central file exists, or when the central file sets inheritance: true.
  • If the repository’s Use organization settings toggle is on, CodeRabbit skips the repository’s saved settings and uses the organization’s. The page still shows the saved settings read-only.
Fix. Remove or adjust the central file, or turn off Use organization settings on the repository’s General page. Turning it off doesn’t copy Organization defaults into the repository, so review its values first. See Settings in the web app and Central configuration.
Cause. Global overrides merge on top of every layer, including a --with-config block and the pull request’s own file. The workspace’s overrides win over the organization’s. Overrides for a key that holds a list add to the list instead of replacing it.Fix. Look for Organization global overrides or Workspace global overrides in the # Source: comment. Change the key in the overrides, or accept that the value is pinned. See Global overrides.
Cause. Invalid YAML syntax or a wrong value type makes the file unusable. The review still runs. CodeRabbit continues with the next layers (central configuration, web interface settings, then defaults) and starts the summary with a <file> has a parsing error warning. Unknown keys in a V2 file don’t fail anything. The summary lists them as unrecognized properties. In a V3 file, an unknown key is a validation error.Fix. Fix the error the warning names, then check the result. See Validate and test a change.
Cause. CodeRabbit rejects version: 3 in a repository as unsupported, except for repositories in the V3 limited preview. It then ignores the file.Fix. Restore the V2 file, or ask CodeRabbit whether your organization is in the preview. Removing only version: 3 leaves V3 keys that V2 doesn’t apply. See Roll back to V2.
Cause. CodeRabbit follows remote_config only when it is the only key in a repository YAML file. If the file has any other key, CodeRabbit doesn’t follow the redirect and doesn’t warn. It parses the file as ordinary configuration. It also doesn’t follow a remote_config inside the fetched file, and it ignores remote_config in TypeScript, central and environment configuration.Fix. Move every other key into the shared file. See Configuration file.
Cause. Use workspace settings as defaults fills only keys that are still empty. A repository or organization whose settings were saved from the form stores every value, including defaults you never touched, so nothing is left to fill. A non-empty list, such as path_instructions, keeps its own entries and gets none of the workspace’s.Fix. For YAML-backed configuration, re-save from the YAML editor view mode so omitted keys are stored sparsely. See Workspace settings.
Cause. CodeRabbit retries a review when it can’t read the repository, the central repository or a remote_config source. After three attempts it drops the review and posts nothing to the pull request. A missing file isn’t an error, so it never causes this.Fix. See Find out why a pull request wasn’t reviewed.

Check the result

Post @coderabbitai configuration again and confirm the setting’s # Source: comment names the layer you edited. If it still names another layer, return to the accordion for that label.

What’s next

Check which configuration a review used

Read the resolved configuration and each value’s source.

How CodeRabbit resolves configuration

Learn the order that decides which layer wins.

Validate and test a change

Catch mistakes before they reach your team’s pull requests.