Setting up Code Review
To set up Code Review for your Unblocked team, select Code Review from the left sidebar. Next, click Set Up Code Review. If you haven’t connected your issue tracker, you’ll be prompted to do so.
Configure Code Review
Once Code Review is enabled, you can adjust the settings to control how reviews are conducted. Click Settings in the sidebar, then select Code Review.Select repositories
Unblocked will automatically review pull requests only for repositories you select.
Code Review user access
Use the Code Review User Access setting to control which users are eligible to receive automated code reviews. By default, All Users is selected, so Unblocked will review pull requests for everyone in your workspace. To limit reviews to specific people, choose Specific Users and select the users you want from the list. Only pull requests authored by those users will receive automated code reviews. Users who are not selected can still request a review manually by mentioning@unblocked in a PR comment. See Requesting a review for details.

Deep Review
Deep Review uses additional analysis and verification to identify subtle bugs and security vulnerabilities that standard review can miss. Multiple agents inspect every reviewable file and evaluate the changes from different perspectives. They analyze what the pull request is intended to do, identify potential correctness and security issues, and independently verify findings against the code before posting review comments. Enable Deep Review when your team needs additional scrutiny for security-sensitive changes or code generated by coding agents. It prioritizes detecting issues that warrant further investigation, so it may surface more findings than standard review. Deep Review uses more credits than standard review. To enable it, go to Settings > Code Review and turn on Deep Review.Approval workflow
Use the Approval Workflow settings to control what happens when Unblocked reviews a pull request and finds no issues.
- Risk Assessment — learn how to define risk policies that Unblocked evaluates against every pull request.
- Comment — post a comment when no issues are found. Turn this off if you want Unblocked to take no action on pull requests that do not qualify for auto-approval.
- Auto-approve low risk Pull Requests — approve pull requests that have no issues and a risk score of
loworlowest. This setting appears when your source control integration supports approvals that count toward pull request requirements. - Legacy Approvals — approve pull requests that have no issues for GitHub organizations whose Unblocked integration does not have the
contents:writepermission. These approvals do not count toward required approvals.
Custom rules
To have Unblocked follow repository instructions during code review, enable repository rules. Unblocked supports a broad range of instruction files and paths; expand the list below to see which ones it recognizes. Coding agents can get the same rules through thecontext_get_rules MCP tool.
Supported instruction files and paths
Supported instruction files and paths
- Root files
- Tool paths
- Rule directories
- Nested files
Markdown instruction filesLowercase forms are also recognized for AGENT.md, AGENTS.md, ARCHITECTURE.md, CLAUDE.md, CONTRIBUTING.md, CONVENTIONS.md, and GEMINI.md.Tool rule files
Examples
For best results, write concise, actionable instructions that reflect your repository and organization’s specific practices rather than general truisms. Good examples:- “Use
event.idfor idempotent event processing.” - “In customer-facing views, format dates with
formatNorthstarDateand the account’s timezone.” - “Use
Moneyfor monetary values; avoid floating-point arithmetic.”
- “Review API changes carefully.”
- “Check for security and correctness issues.”
- “Make sure database changes are safe.”
Excluded paths
You can configure custom path exclusion patterns to exclude specific files or directories from review. These patterns use glob syntax and are applied when processing pull requests. Common exclusion patterns include*.md to exclude all Markdown files at any depth, src/test/** to exclude all files under a specific directory from the repository root, and package-lock.json to exclude specific files. You can also exclude entire directories like node_modules/** or file types like *.generated.js.

Select a bot account
- Azure DevOps
- Bitbucket Cloud
- Bitbucket Data Center
- GitLab Cloud
- GitLab Self-Managed
For Azure DevOps repositories, code review comments need to be posted on behalf of an Azure DevOps user account. We recommend creating an Unblocked bot account for this specific purpose.
1
Create a bot account
- In the Microsoft Entra admin center, go to Entra ID > Users.
- Click New user, then select Create new user.
-
Create a new user with the following information:
- Name: Unblocked
-
Avatar: download and use the Unblocked logo below
Download PNG
- In Azure DevOps, sign in to your organization as a Project Collection Administrator.
- Click Organization settings > Users, then click Add users.
- Enter the bot user’s email address.
- Set Access level to Basic.
- Under Add to projects, select each project where Unblocked should review pull requests.
- Set Azure DevOps Groups to Project Contributors.
- Click Add.
2
Select your Bot Account
In Unblocked, search for the bot account you just created and select it. You may be required to authorize this account with Unblocked.
