Pull-request integration

Check runs, annotations, merge gates and exceptions.

Check run

On GitHub, each scan posts a check run named TrustLedger AI Governance to the pull request; on GitLab and Bitbucket the result is posted as a commit or build status. The check run's summary lists the files by risk, and the pull-request comment and the review page carry each finding with its line, trace and suggested fix.

Merge gate

The merge gate decides which unattested files block the merge. Organisations choose in Settings whether CRITICAL files, HIGH files, or both block; by default both do. It fails closed: if the setting cannot be read, files block. Files that do not block still need review — their findings stay open, they just do not hold the merge. To enforce it, make the check a required status check in your branch protection rules.

Clearing a block

  • Fix the code — the next push is rescanned; a fixed file no longer blocks.
  • Attest the file — a named reviewer signs off on the file as it is (see Attestation); the check run is re-synchronised.
  • Triage the finding — a security reviewer or admin marks it a false positive or accepts its risk, with a reason and optionally an expiry. The decision follows the finding's stable fingerprint across pushes and pull requests, takes effect on the next scan, and is written to the audit log.

Policies

Two presets exist. Standard blocks CRITICAL and HIGH files until one attestation each and flags files over 65% AI-generated for review. Strict also blocks MEDIUM files, requires two attestations for CRITICAL files and a designated reviewer, and flags files over 50%.

Next: Attestation →