Before you start
- Run the steps in the next section first. They show you which layer supplied the value.
- Know the configuration priority and how inheritance and merging work.
Find which layer supplied the value
- Post
@coderabbitai configurationas a comment on a pull request. See Check which configuration a review used. - Find your setting in the YAML and read its
# Source:comment. - Open the accordion below that matches the label or the symptom.
Match the symptom
The value comes from the wrong branch, or a pull request ignores its own file
The value comes from the wrong branch, or a pull request ignores its own file
Your TypeScript configuration is ignored
Your TypeScript configuration is ignored
.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.Organization or central values are ignored in a repository that has its own file
Organization or central values are ignored in a repository that has its own file
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.Settings you saved for a repository in the web interface have no effect
Settings you saved for a repository in the web interface have no effect
- 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.
A global override wins over your setting
A global override wins over your setting
--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.Your repository file is dropped and the summary shows a parsing error
Your repository file is dropped and the summary shows a parsing error
<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.A file with version: 3 is ignored
A file with version: 3 is ignored
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.Workspace defaults don't fill your gaps
Workspace defaults don't fill your gaps
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.No review appears and nothing is posted
No review appears and nothing is posted
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.