attest How Attest works
From a pull request to an evidence-backed result.
The journey
- A GitHub event or an authorized manual command requests work for a pull request. Attest associates the run with its exact head commit.
- Attest finds a preview from GitHub-visible metadata and checks its association with that commit. An ambiguous or unverified preview cannot produce a pass.
- A model examines bounded pull request context and uses constrained tools to explore the preview in an isolated browser. Attest does not generate customer test scripts.
- A separate review and deterministic checks evaluate recorded evidence. Missing evidence or a blocked run is inconclusive rather than a pass.
- Attest reports the result through a GitHub Check and a maintained summary where supported. The Check is associated with the tested commit.
A new commit supersedes work on the old one. Before relying on any result as a required merge check, validate GitHub behavior in your own controlled repository; the real required-check acceptance gate remains open.
Continue with requirements or read about results and evidence.