GitHub Actions AI PR check

Run an AI pull request check in GitHub Actions.

Abizor installs from PyPI, reads the pull request diff in the runner, creates a replayable event log, exports a Change Record, and publishes a GitHub Check projection.

InstallPyPI package
Runs inyour Actions runner
Verifiesproof bundle
Mergenot in quickstart

This page is for

Teams implementing the Abizor check in GitHub Actions.

Use this page when the question is practical: how the Marketplace action runs in a GitHub Actions workflow, installs Abizor from PyPI, publishes a Check, and points back to the main copy-paste quickstart.

What the workflow does

A CI-native check for the AI change state behind the PR.

The quickstart checks out the named pull request branch, installs Abizor from PyPI with python3 -m pip install abizor==0.1.7, runs abizor ci-proof, and uploads proof artifacts.

The proof bundle includes an event log, artifact manifest, Change Record JSON, Change Record Markdown, summary, PR comment body, and optional redacted feedback export.

Quick boundary

The quickstart is bounded by default.

DoesReads checkout state, creates proof artifacts, and publishes a Check projection.
Does notCreate PRs, merge PRs, deploy code, or use hosted Abizor infrastructure.
Canonical truthThe Abizor event log generated by the run.
Local verificationabizor verify-proof recomputes hashes and regenerates the Change Record from the event log.

Copy-paste path

Start from the current quickstart.

python3 -m pip install abizor==0.1.7

abizor ci-proof --event-log "$RUNNER_TEMP/abizor-events.json" ...

Install the GitHub Actions proof workflow.

The full workflow includes checkout, PyPI install, artifact upload, and local proof verification.

Open quickstart Read target proof