GitHub pull requests
Proof watches pull-request changes, selects the affected business scenarios, runs bounded checks, and reports through GitHub Check Runs.
When Proof runs
The GitHub App responds to non-draft pull requests when they are opened, reopened, updated, or marked ready for review. Signed deliveries are deduplicated so GitHub retries do not create duplicate work.
How scenarios are selected
Proof fetches every changed file and compares it with revision-scoped coverage links. It selects up to three affected scenarios with an explanation. If no exact coverage matches, it uses a bounded high-priority fallback.
When AI is enabled, Proof also rebuilds the flow and edge-case model at the pull request commit so new behavior can grow the catalog. When AI is paused, it runs only scenarios that already have active deterministic tests.
Read the Check Runs
Each selected scenario gets a Check Run named Proof / <scenario-id>. A separate Proof / flow and edge discovery check tracks exact-commit catalog discovery. The check summary explains why the scenario was selected and links to the durable run.
Administrator setup
Configure GITHUB_APP_ID, GITHUB_PRIVATE_KEY, and GITHUB_WEBHOOK_SECRET. Set the webhook URL to https://your-proof-host/api/webhooks/github, subscribe to pull-request events, and grant the app access to pull requests, repository contents, and Check Runs.