PR Checks & Merge Gate

Reshot posts the reshot/visual-review commit status for every publish tied to a pull request. The status links to one before-and-after matrix grouped by flow and context.

State model

Status	Meaning
`pending`	At least one changed flow × context result awaits a decision
`success`	Every changed result was approved
`failure`	A reviewer rejected at least one changed result

The check is recomputed after every decision. A rejection continues to block the merge even if other results are still pending.

Enable the required check

Install the Reshot GitHub App and connect the repository in project Settings.
Add npx reshot run --headless and reshot publish to pull-request CI.
Publish Git metadata including the head commit SHA and pull-request URL.
In the repository branch rules, require reshot/visual-review before merge.

GitHub only offers a status context in branch rules after it has been posted at least once. Run one PR capture before configuring the rule if it is not listed.

Review the matrix

Open the status target or Reshot's PR summary comment. Each card shows the previous approved image and the new candidate for one flow and context. Drag the comparison slider, then approve or reject the change. Product, design, QA, or engineering reviewers can make the decision without repository access when you send them an existing Reshot review share link.

Make CI send PR metadata

The publish payload accepts the head commitHash, branch, commit message, author, and pullRequestUrl. Reshot stores those values on the publish event so the review evidence, GitHub status, comment, and audit trail all refer to the same change.