Make Audit Bench Ai a required check

Before you start

The Audit Bench Ai GitHub App is installed on the repository (in the app: Repository scan → GitHub → Install on GitHub).
It has reviewed at least one pull request there. GitHub only lists checks it has seen recently, so open any small PR first and wait for the Audit Bench Ai check to appear on it.
You’re an admin of the repository (or the organization).

In the repository, open Settings → Rules → Rulesets and choose New ruleset → New branch ruleset.
Name it, for example “Require Audit Bench Ai”, and set Enforcement status to Active.
Under Target branches, choose Add target → Include default branch (or add the branches you protect).
Tick Require status checks to pass, then Add checks, type Audit Bench Ai and select it.
Click Create.

Organization admins can do the same once for every repository under the organization’s Settings → Repository → Rulesets.

In the repository, open Settings → Branches and choose Add classic branch protection rule.
Enter the branch name pattern, for example main.
Tick Require status checks to pass before merging, search for Audit Bench Ai and select it.
Click Create.

Failure: a critical issue in the changed lines. The pull request can’t merge until it’s fixed.
Neutral: issues worth a look, but nothing blocking. GitHub treats this as passing, so the merge isn’t held up.
Success: no issues in the changed lines.

Fix the issue and push. Every new commit is reviewed again and the check updates by itself.
If the finding is wrong, reply to its comment explaining why. Audit Bench Ai rechecks and answers, and it learns to stop raising that kind of comment. Then click Re-run on the check in the pull request’s Checks tab to review the latest commit again.
In an emergency, repository admins can bypass the rule if your ruleset allows it (add them under Bypass list).

See how Audit Bench Ai handles your code on the Security & Trust page, or contact us.