FAQ

Which VCS integrations are supported?

PR Review works with the GitHub and GitLab integrations. A project must be bound to a repository from one of these connections.

The review itself is the same on both: one summary comment, edited in place as you push, plus inline comments on the findings that carry a fix or a high severity. The status object differs. GitHub gets a check run; GitLab gets a commit status, which GitLab records as a pipeline job. See GitLab for what that means for a project with no CI.

How does PR Review differ from a code audit?

A code audit is a full assessment of your codebase. PR Review is a project-level continuous capability that audits only the changed paths of a pull request and posts inline comments. It is not a full assessment. For complete coverage, run a code audit or use Source Code Audit.

On which repositories can PR Review comment?

PR Review posts comments on pull requests in any repository you grant to the GitHub or GitLab integration and bind to a project. The integration must have pull-request webhook permissions for the target repository.

How much does each review cost?

Each PR review consumes credits per review. Duplicate deliveries for one PR head within the selected Project produce one review and one debit. If PR review moves to another Project, later runs use that Project's own security context and history. See Credits & billing.

How do I know why a PR was not reviewed?

Open the project's Source tab and inspect the delivery log. Delivery rows show the repository, commit, event type, status, and a readable ignored reason such as an unbound project, branch filter mismatch, or disabled PR review. See How it works.

Is PR Review a full assessment?

No. It reviews only the changed paths of a pull request and returns inline comments, not a full findings report. For a full assessment of your codebase, use code audit.