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.

A Bitbucket connection gives a project its source, its assessments and its scans. AISafe does not review Bitbucket pull requests yet.

The review format is the same across providers: 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 continuous capability of a project 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. Bitbucket repositories are not reviewed yet.

How much does each review cost?

Each workspace pays for its own review attempts. Each new push or authorized request uses one included review, then costs $1 when the allowance is exhausted. A push containing several commits produces one review of its latest commit. Duplicate deliveries and internal retries reuse that attempt. Adding funds does not restart a refused review; comment @aisafe review, use Retry review, or push a new commit. See Credits & billing.

What happens to PR review if my plan changes?

Your repository settings stay as they are. Each new commit gets a completed, neutral check titled "AISafe PR review paused: plan doesn't include PR review", so a branch rule that requires the AISafe check never blocks a merge. Reviews already running finish. Reviews resume on the first push after you upgrade. 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 instead of a full findings report. For a full assessment of your codebase, use code audit.

Can one project review several repositories?

Yes. Connect several repositories from the same provider (up to five on the Free and Pro plans, with no limit on Enterprise), then configure PR review for each repository independently. Each PR review uses the complete application context and keeps the companion repositories at a fixed commit during the comparison. For an application of more than five repositories, write to sales@aisafe.io.

Can two projects claim the same repository?

Within one workspace, you explicitly select one project for a repository's PR reviews. AISafe refuses a competing selection instead of silently dropping one of the projects. Different workspaces may each select a project; each of them receives independent reviews, comments, checks, results, and charges.

Why did the required check name change?

Each workspace and project now publishes its own check. Copy its exact name from PR Reviews → Settings and update branch protection rules that require the old generic name. AISafe preserves ambiguous old comments and checks rather than letting one workspace overwrite another's history.

What happens when I add or remove repositories?

Saving the change resets the entire living knowledge base after active runs finish. Historical assessments, reports, findings, and revisions remain available. New runs pause while a change is pending. Setup shows a retry action if the change needs to resume.

Why did my review fail?

If a review run fails on AISafe's side, AISafe runs it again by itself before it reports anything, so you never need to push a commit or retry a review to get one. When a review still does not finish, AISafe says so on the review in AISafe and in the check run on the pull request, and says what to do next when there is something for you to do.

What you see	What to do
AISafe could not finish this review. It was not charged, and there is nothing you need to do.	Nothing. AISafe already ran the review again before it showed this, and its team has the details. Your next push is reviewed as usual.
AISafe could not start this review. It was not charged, and there is nothing you need to do.	Nothing. Your next push is reviewed as usual.
Review not started because the repository source could not be retrieved. Try again when repository access is restored.	Check the repository connection in AISafe, then choose Retry review.
This pull request changes only generated, binary or vendored files.	Nothing. There was nothing to review.
The review finished and the provider refused to post it on this pull request.	Check the three things the sentence names: the AISafe app's write access to the repository, a branch rule rejecting its check, and whether the pull request is still open. Fix the cause, then choose Retry review. The findings are already on the review in AISafe.

A review that did not finish is refunded. Retrying one is charged like any review.

A review the provider refused is refunded too, and it keeps its findings, because the analysis finished and only the delivery to the pull request failed. You can read the findings on the review in AISafe while you fix the cause of the refusal.