Code review
Triggers and skip rules
Pick which pull request events start a review, and skip the pull requests that don’t need one.
Triggers and skip rules live on the Triggers tab of the Code review page and apply to every repository you turned on. When a skip rule matches, Codebot posts a skipped check on the pull request that says which rule matched and how to get a review anyway.
@trycodebot review always runs a review, past every skip rule except forks on Azure DevOps. See Review on demand.
When to review
Choose the pull request events that start a review:
- Opened: a new pull request.
- Commits pushed: new commits on an open pull request. Later reviews focus on what changed since the last one.
- Ready for review: a draft is marked ready, or a closed pull request is reopened.
Skip rules
Skip drafts
Don’t review draft pull requests. Pair it with Ready for review to get one review when the author is done.
Skip bots
Don’t review pull requests opened by bots, like Dependabot or Renovate on GitHub, or build service accounts on Azure DevOps.
Skip forks
Don’t review pull requests from forks. On by default. See Pull requests from forks before turning it off.
Ignored authors
Authors whose pull requests are never reviewed automatically: GitHub usernames, or Azure DevOps sign-in emails or display names.
octocat, release-bot, jane@contoso.comBase branches
Only review pull requests into these branches. Use * as a wildcard. Leave it empty to review pull requests into any branch.
main, release/*Skip keywords
Skip pull requests whose title contains any of these words.
[skip review], WIPIgnored files
Files Codebot leaves out of the review, one pattern per line, like .gitignore. A pull request that only changes ignored files is skipped.
*.lock
pnpm-lock.yaml
**/__generated__/**
docs/**Maximum changed lines
Skip pull requests that change more lines than this. Leave it empty for no limit. Ignored files don’t count.