CodeRabbit doesn’t review a pull request that changes more files than your plan allows. See the files-per-review limits in Plans. The limit counts only the files left after path filters, so if your pull requests often hit it, exclude files that don’t need review, such as generated code, localization files or snapshots.
How path filters work
Each entry inpath_filters is a glob pattern. A pattern that starts with ! excludes files. A pattern without ! includes them.
- Patterns are
Minimatchglobs, matched against repository-relative paths. Matching is case-insensitive, hidden files (names starting with a dot) are included, and there are no gitignore rules. - A file is reviewed only if it matches at least one include pattern, when you set any, and it matches no
!pattern. - Exclusions always win, whatever the order of the entries.
- CodeRabbit adds its default exclusions in front of your list.
Configure
- In the app
- YAML V2
- YAML V3
Open Review settings, choose Organization defaults or a repository, and set View mode to All Settings. Go to Reviews > General and find Path filters. Select Apply changes and confirm.
Keep path filters from becoming an allowlist
Any include pattern limits review to the files it matches, unless it exactly matches a default exclusion. CodeRabbit accepts a list with only include patterns and doesn’t warn you.Review only src
Review everything except two folders
Files skipped by default
CodeRabbit skips these groups of files unless you override them.
Shader sources such as
*.hlsl, *.glsl and *.shader are reviewed by default. CodeRabbit drops the entries **/*.hlsl, **/*.glsl and **/*.shader from your path_filters, so they don’t turn your list into an allowlist.
Every default pattern
The groups below list every pattern CodeRabbit adds in front of yourpath_filters. To review a skipped file type, copy its pattern without the leading !, as described in Review files that are skipped by default.
Build and dependency folders
Build and dependency folders
Lock files
Lock files
Generated code
Generated code
Compiled files and binaries
Compiled files and binaries
Archives and disk images
Archives and disk images
Audio and video
Audio and video
Images and fonts
Images and fonts
Documents and data
Documents and data
Logs, maps, checksums and editor files
Logs, maps, checksums and editor files
Minified and bundled output
Minified and bundled output
Bundlers write production assets with a content hash in the file name, often outside
dist and without .min. The last four patterns match that shape. Each [0-9a-z_-] class is one hash character, the URL-safe alphabet that Rollup and Vite use by default, written out eight times because glob patterns have no repetition syntax. Matching is case-insensitive, so assets/index-DUKDdC5R.js matches too.The hash width keeps most hand-written files in review: assets/index-page.js and src/editor.chunk.js are reviewed. A hand-written name whose segment is exactly eight of these characters, such as assets/index-my-thing.js, is skipped. To review it, add the matching pattern without the !.3D and game assets
3D and game assets
Language and tool files
Language and tool files
Other file types
Other file types
Review files that are skipped by default
To review a skipped file type, add its exact default pattern without the!. This removes the default exclusion and does not create an allowlist.
The same applies to folders that only look generated. CodeRabbit matches
gen and generated at any depth, so hand-written code in a folder with either name is skipped until you add the exact pattern.
Where filtered files show up
- Filtered files don’t appear in the walkthrough or the Change Stack. Your Git provider still lists them in the pull request’s file list.
- When path filters exclude every changed file, CodeRabbit skips the review with the reason No files to review. The review finishes as a successful no-op, so a required
CodeRabbitcheck passes. See CodeRabbit status check.
Limits and availability
- Path filters work on every Git platform and apply to organization defaults and repositories.
- Path filters also shape the repository checkout, and Git’s sparse-checkout rules differ from review matching. Tools can see a different file set than the review.
- On Azure DevOps, the default exclusions apply directly to repository inventory and diff hydration, so an override doesn’t take effect on those two paths.
- IDE reviews apply the default list after the extension’s own exclusions.
- Schema V3 is a limited preview.
Troubleshoot
- A file you expected in review is missing: check the default list above, then look for an include pattern that created an allowlist. Print the resolved filters with Check which configuration a review used.
- No review ran on a pull request that only changes lock files or generated code: see Find out why a pull request wasn’t reviewed.
reviews.path_filters in the configuration reference. V3 key: reviews.behavior.path_filters.
What’s next
Teach CodeRabbit your review rules
Give guidance for the files that stay in review.
Configure a monorepo
Scope filters and instructions by package.
Reduce review noise
Combine filters with profile and instructions.