Run a deep review

Use Deep Review to investigate a pull request with a separate credit budget and runtime limit. You can add a focus for the investigation.

Set the organization policy#

Ask an administrator to configure Organization → Reviews → Automation before starting a deep review.

1. Find Deep review and set Availability to Manual or Automatic.
2. Enter Maximum credits per deep review.
3. Set Maximum duration, in seconds.
4. Save the review settings.

Manual allows a person to request a deep review. Automatic also allows configured triggers to request one. Disabled prevents deep reviews.

Start from a pull request#

1. Open the pull request from Pull requests, or open one of its reviews.
2. Select Run deep review.
3. Enter a Focus (optional), such as “Check whether this migration is compatible with the previous application version.”
4. Select Start deep review.

The action reviews the current pull request head and opens its run. If a deep review already exists for that head, the action opens the recorded run. Its original focus stays fixed.

Check the recorded commit before using the result. A deep review does not replace the earlier review or establish an environment assessment that could not finish.

Request deep reviews automatically#

In the organization's Deep review settings, choose Automatic and enter repository-relative patterns under Sensitive paths (one pattern per line). For example, migrations/** requests a deep review when a change touches that directory.

Allow automatic risk escalation also permits escalation from an ordinary review. Review the confirmation before saving an automatic policy; matching changes can spend the configured deep review budget.

To restrict one repository, open Organization → Repositories, select it, and open Automation → Deep Review. Choose Same as the organization or a more restrictive Availability. A repository cannot enable a mode beyond the organization's policy.

In automatic mode, you can clear Use the organization's sensitive paths and enter repository-specific patterns. Leave the list blank to turn off that repository's path triggers. Select Save Deep Review policy, then confirm if requested.

Resolve a refused request#

Read the error before trying again. A missing credit budget requires an administrator's change. Disabled policy or missing repository access also needs to be resolved before a run can start.