- PRs with specific titles (using regex matching)
- PRs between specific branches (using regex matching)
- PRs from specific repositories (using regex matching)
- PRs not from specific folders
- PRs containing specific labels
- PRs opened by specific users
- PRs generated files by language/framework
- Ignore tickets with specific labels
Configure ignore rules in the Qodo portal (Recommended)
- Log in to the Qodo portal.
- Navigate to Configurations > Workflow > Ignore PRs.
- Configure the title, author, label, and branch settings.
Configure ignore rules in .pr_agent.toml
If you’re not using the portal, configure any of the settings below directly in your.pr_agent.toml file.
Ignore PRs with specific titles
To ignore PRs with a specific title such as “[Bump]: …”, you can add the following to your configuration file:ignore_pr_title is a list of regex patterns to match the PR title you want to ignore. Default is ignore_pr_title = ["^\\[Auto\\]", "^Auto"].
Ignore PRs between specific branches
To ignore PRs from specific source or target branches, you can add the following to your configuration file:ignore_pr_source_branches and ignore_pr_target_branches are lists of regex patterns to match the source and target branches you want to ignore. They are not mutually exclusive, you can use them together or separately.
Ignore PRs from specific repositories
To ignore PRs from specific repositories, you can add the following to your configuration file:ignore_repositories is a list of regex patterns to match the repositories you want to ignore. This is useful when you have multiple repositories and want to exclude certain ones from analysis.
Ignore PRs not from specific folders
To allow only specific folders (often needed in large monorepos), set:Ignore PRs containing specific labels
To ignore PRs containing specific labels, you can add the following to your configuration file:ignore_pr_labels is a list of labels that when present in the PR, the PR will be ignored.
Ignore PRs from specific users
Qodo tries to automatically identify and ignore pull requests created by bots using:- GitHub’s native bot detection system
- Name-based pattern matching
- Bots are registered as regular user accounts
- Bot names don’t match common patterns
ignore_pr_authors is a regex list of usernames that you want to ignore.
There is one specific case where bots will receive an automatic response - when they generated a PR with a failed test. In that case, the
ci_feedback tool will be invoked.Ignore generated files by language/framework
To automatically exclude files generated by specific languages or frameworks, you can add the following to your configuration file:generated_code_ignore.toml. Files matching these glob patterns will be automatically excluded from PR Agent analysis.
Ignore tickets with specific labels
When Qodo analyzes tickets (JIRA, GitHub Issues, GitLab Issues, etc.) referenced in your PR, you may want to exclude tickets that have certain labels from the analysis. This is useful for filtering out tickets marked as “ignore-compliance”, “skip-review”, or other labels that indicate the ticket should not be considered during PR review. To ignore tickets with specific labels, add the following to your configuration file:ignore_ticket_labels is a list of label names that should be ignored during ticket analysis.
Ignore PRs opened by bots and AI agents
By default, Qodo does not review pull requests opened by bot accounts:-
The Git platform marks the author as a bot, such as a GitHub App account like
my-agent[bot]. -
The author’s username matches a bot-like heuristic. This includes fragments such as
-bot,[bot],jenkins,service,cicd, orassistantas a separate word, as well as the exact usernamesclaude,augment, andcodex. Ordinary human-owned service accounts, such asdeploy-jenkins-ci, may also match. -
The PR description contains an automation phrase such as
This PR was created automatically by.
Enabling reviews for bot PRs
To enable reviews for PRs opened by bots, including AI coding agents, add the setting to.pr_agent.toml under the section for your Git provider:
ignore_bot_pr, the setting falls back to the value under [config] (default true). Setting ignore_bot_pr under [config] applies to every provider unless a provider’s own section overrides it. Placing it under [github] (without _app) has no effect.
Place .pr_agent.toml at the repo root on the default branch so the Qodo app can read it. For an org-wide default, add it to the root of a repository named pr-agent-settings in your organization, which the Qodo app must have access to. The setting takes effect on the next PR the bot opens.
Reviewing selected bot PRs while keeping other bots ignored
Settingignore_bot_pr = false enables reviews for every bot author. To keep specific bots excluded, combine it with ignore_pr_authors, which accepts regular expressions matched against the author’s username:
Rules and guidelines
-
A team member can always trigger a review on a bot-authored PR by commenting
/agentic_review, even whenignore_bot_pris set totrue. -
This setting affects PRs opened or updated by bots. Comments posted by bot accounts receive a response only when they contain slash commands such as
/qodo <question>or/agentic_review. Mentions such as@Qodofrom bot accounts are ignored. -
On self-hosted deployments using the classic GitHub App webhook server, the repository-level override may not apply. In that case, set
ignore_bot_pr = falsein the deployment configuration instead. Classic self-hosted deployments for GitLab, Bitbucket Data Center, and Azure DevOps do not have a deployment-level switch for this setting.
Related resources
- Trigger a code review: Run reviews automatically or manually.
- Customize the code review experience: What you can configure, and where to configure it.