Every repository you connect to Code Reviews has its own Settings page in Gearset, where you control which branches Code Reviews scans, how it behaves on pull requests (PRs), and which rules it checks your code against.

To get there, select a repository, then click Settings in the top right of the Code Reviews tab.

Tracked branches

A tracked branch is a branch that Code Reviews monitors so it can trigger scans automatically. The Tracked Branches tab lists the branches Code Reviews is currently tracking for the selected repository.

To track a new branch, select it from the Select a branch dropdown. To stop tracking a branch, click the x next to its name.

Tracking only the branches that matter to your team, rather than every branch in the repository, keeps scan reports focused on your production-critical branches and avoids unnecessary scans of short-lived feature branches.

Configuration

The Configuration tab controls how Code Reviews scans the branches you're tracking, and how it behaves on PRs.

General

Exclude issues introduced before a selected date sets a reference date and treats any issue introduced before it as legacy code, so it's excluded from scan results. This helps reduce noise in codebases with existing technical debt by keeping the focus on new issues.
Under Code Reviews app, the Access Code Reviews App button opens the legacy Code Reviews app, where you can access legacy features and functionality.
Under Webhook, the Create webhook button sets up the webhook Code Reviews needs to trigger scans automatically and on a schedule.

Code Reviews on PRs

This section controls how Code Reviews reviews pull requests, and how strictly it enforces compliance. It's the equivalent of choosing a protection mode such as "Protect what's new", broken down into individual settings.

Enable Automated Code Reviews on PRs in tracked branches — performs Code Reviews scans of new pull requests on the branches you're tracking.

Note: Without a webhook, Code Reviews won't be notified when PRs are opened or updated, so set up a webhook using the Create webhook button before relying on this setting.

Version Control System (VCS) behaviour

Publish branch status checks on PRs publishes the violations found across all files in the revision scan as a status check on the PR, giving visibility into the overall codebase health rather than just the PR's own changes.
Publish a review on PRs in VCS publishes a summary of the scan as a review directly on the PR in your VCS.
Publish individual comments for issues adds individual comments on the PR for each issue Code Reviews finds, either inline on the affected line or as a threaded comment, depending on the rule and VCS. You can limit this to Up to 20 comments per PR, or allow All.
Allow Code Reviews to act as an approver on PRs lets Code Reviews act as an approver alongside your human reviewers. When a PR has no violations, Code Reviews can automatically approve it for promotion.

Gating on PRs

Code Reviews can act as a deployment gate and block PRs that have violations, but this has to be set up as a branch protection rule (also called a quality gate) in your VCS. Code Reviews itself doesn't block merges. See the setup guide for your VCS:

Rules

The Rules tab lists every rule Code Reviews can scan your code against, along with its severity (Warning, Error, or Critical) and whether it's currently switched on for this repository. Use the toggle next to a rule to turn it on or off. To edit the rules used to scan your code in more detail, use the Code Reviews app.

With dozens of rules available, use the filters above the table to find the ones you need:

Search rules finds a rule by name.
Metadata types filters rules to only those that apply to a specific metadata type, such as Agentforce, Apex, Aura, Flow, LWC, Metadata, or Visualforce.
Tags filters rules by tag.
Severity filters rules by severity level.
Status filters rules by whether they're enabled or disabled.

For a full list of available rules, see the Code Reviews rules summary.

Code Reviews repository settings: tracked branches, configuration, and rules