Abizor
Menu

Public proof

GitHub Actions CI proof on a real pull request.

This public proof summarizes a real GitHub Actions run of Abizor against an existing pull request. It is a public summary of the proof boundary; raw event-log artifacts are identified by hash, not published on this page.

Date2026-06-07
Resultmerge boundary reached
Steps11
PR closureclosed, no merge

What was verified

Abizor ran from a normal pull request workflow.

Abizor ran in GitHub Actions on pull request #3 in the Abizor repository.

It checked out the PR head branch, read the existing diff, ran the configured verification command, read checks, and reached the merge boundary.

The workflow uploaded the proof record, human summary, generated PR comment body, and artifact manifest.

What Abizor did

It kept the PR reviewable and stopped before delivery.

  • Used an existing GitHub Actions checkout.
  • Ran abizor ci-proof without --patch-file.
  • Produced a replayable abizor-events.json event log.
  • Restored the run to MERGE with next action merge_pr.
  • Did not execute merge_pr.

Output

The final output reached the merge boundary.

Status: merge boundary reached
Diff evidence: existing checkout diff origin/main...HEAD
Steps run: 11
Boundary: merge_pr was not executed.
Next step: Review the event log and generated comment body artifact.

Artifact hashes

Public hash references for the generated artifacts.

The event log is not published on this public page. The proof keeps the artifact names and SHA-256 hashes so the run can be identified without requiring public access to raw generated artifacts.

abizor-events.json5df7a88895bc98b2fdeac0883df4cca5582c9280eb1e50579b672eefe45b620f
abizor-summary.md8f6d721bcfd0fa8a80b9c6f45630d59d74480e686c00b04881b1bcc07eb2108f
abizor-pr-comment.md8f6d721bcfd0fa8a80b9c6f45630d59d74480e686c00b04881b1bcc07eb2108f
abizor-artifacts.json6e484e802257f8c690c6fc9f822cc5fcee54490ab572fd1751b29826bb6e5396

Boundary

What this proof does not claim.

This proof did not create or merge the pull request.

It did not deploy code, post a PR comment, or use a hosted app, hosted API, dashboard, billing flow, or GitHub App.

It is not a compliance, security-audit, or production-deployment claim.

Run the same kind of proof.

The public quickstart shows the current self-serve CI path.

Open quickstart Back to trust