Product guide · English
Review pull requests
Enable PR Delta Review for an eligible repository connected through the GitHub App, GitLab.com or Bitbucket Cloud, then make the vetkit / PR Delta Review status required in your provider if you want it to block merges.
Steps
- In repository settings, verify the provider connection (GitHub App, GitLab.com or Bitbucket Cloud) and that the workspace has access to PR Delta Review. Enable it and review the applicable severity, category and policy settings.
- When a pull request opens or changes, inspect the head and merge-base audits. Delta review uses comparable checks and reports newly introduced findings on added lines.
- Read the vetkit / PR Delta Review status and its summary; new findings on added lines also receive inline comments. Check-run annotations and component-policy results are posted on GitHub only. Inspect incomplete or failed analysis rather than assuming the PR is clean.
- Configure the status as required in GitHub’s branch protection or ruleset, or the equivalent merge check in GitLab or Bitbucket, when appropriate. Re-run review after a fix and confirm the result refers to the current PR revision.
Read the result
Delta review focuses on introduced risk; it is not an inventory of every pre-existing issue. Code and component gates carry different evidence. A successful workflow that merely downloads a report is not the same as a required policy check.
Limits and availability
Provider authorization and feature access are required; Free Quick Scan alone does not enable PR automation, and self-hosted GitLab is not supported. A posted status cannot prevent a merge unless the repository’s rules require it. Static review does not replace application tests or human review.
This guide describes the implemented workflow. The features available in your workspace depend on account capabilities and configuration; advanced workflows are not all included in Free Quick Scan. Check the available controls and the evidence returned by each run.