Exclude dependency bots and automated updates from reviews
How it works
1
Check PR author
CodeRabbit checks if the PR author’s username matches any in your
ignore_usernames
list2
Skip if matched
If the username matches exactly (case-sensitive), the review is skipped silently
3
Continue if not matched
If no match, CodeRabbit continues with normal review processing, including label checks
4
Manual override available
Use
@coderabbitai review
to force a review even for ignored usersConfiguration
Add theignore_usernames
array to your .coderabbit.yaml
file:
Username matching is exact and case-sensitive. Verify the exact username format on your Git platform. For example, GitHub bots use
[bot]
suffix.Configuration | PR Author | Review Status | Comment Posted |
---|---|---|---|
[] (empty) | Any user | ✅ Reviewed | Yes (if applicable) |
["bot-user"] | bot-user | ❌ Skipped | No (silent skip) |
["bot-user"] | other-user | ✅ Reviewed | Yes (if applicable) |
["user1", "user2"] | user1 | ❌ Skipped | No (silent skip) |
["User1"] | user1 | ✅ Reviewed | Yes (case mismatch) |
Integration with other features
Username-based skipping takes precedence over other controls:Processing order: Username check → Label check → Other review rulesIf a user is in
ignore_usernames
, their PR is skipped regardless of labels or other settings.Migration from labels only
Manual review override
Even for ignored users, you can trigger reviews manually:Best practices
Use for permanent exclusions
Use for permanent exclusions
Username-based ignoring works best for users you want to permanently exclude:
- Automated bots (dependency updates, security scanners)
- Service accounts (CI/CD, deployment automation)
- Trusted senior developers who consistently self-review
wip
or draft
instead.Verify exact usernames
Verify exact usernames
Username matching is strict. Check the exact format on your platform:
- GitHub:
dependabot[bot]
,renovate[bot]
,github-actions[bot]
- GitLab:
gitlab-ci-token
,project_123_bot
- Azure DevOps: Service account names without special formatting
Document your choices
Document your choices
Maintain a list of ignored users and reasons:
Regular review
Regular review
Periodically review your ignore list:
- Remove accounts that are no longer active
- Add new automation accounts as they’re created
- Verify usernames are still accurate after platform changes
Limitations
- No wildcard support: Cannot use patterns like
*[bot]
ordependabot*
- No regex support: Must specify exact usernames
- Case-sensitive matching:
User1
anduser1
are treated as different users - Platform-specific formats: Username formats vary between Git platforms
- No team/group support: Cannot ignore entire teams or organizations
Troubleshooting
PR still being reviewed
Problem: A user in your ignore list is still getting reviews. Solutions:- Check exact username: Copy the username directly from the PR author field
- Verify case matching: Ensure capitalization matches exactly
- Check configuration syntax: Confirm YAML array format is correct
- Validate configuration deployment: Ensure
.coderabbit.yaml
changes are committed
Want to review an ignored user’s PR
Problem: Need to review a PR from someone on your ignore list. Solutions:- Use manual review: Comment
@coderabbitai review
on the PR - Temporary removal: Remove username from ignore list, commit, then re-add
- Use labels: For occasional reviews, consider label-based controls instead
Commit status
When a PR is skipped due to username filtering:- Status message: “Review skipped: Author is ignored by configuration”
- No summary comment: The skip is silent to avoid noise
- Logged for debugging: The skip reason is recorded for troubleshooting