The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →To approve a visual change in Chromatic, open the build linked to your pull request and accept each changed snapshot that is intentional; deny a regression. That updates or rejects the image baseline, not the team’s sign-off on the pull request. For stakeholder approval, review the pull request’s separate UI Review, resolve discussions, and approve the review. If merge approval must be enforced, require the appropriate Chromatic status check in your Git provider.
First, distinguish snapshot acceptance from pull-request approval
Chromatic’s UI Tests compare the current story snapshots with accepted baselines and run visual and interaction checks in CI. Accepting a changed snapshot updates the reference image used in later comparisons; denying a change marks it as denied and fails the build. This is a decision about the visual baseline, not a declaration that the whole team has approved the pull request. See Chromatic’s pull request workflow and its Quickstart.
UI Review is a separate stakeholder workflow. It presents the changes between the pull request’s head branch and base branch, supports assigned reviewers and discussions, and tracks sign-off. The UI Tests check for changes and regressions; UI Review is for people to assess and approve intended changes. A Git-provider status check can report either workflow, depending on configuration.
Accept or deny changed snapshots
- Open the Chromatic build linked from the pull request.
- Inspect every changed story snapshot and its diff against the accepted baseline.
- Accept a change only when it is intentional. Acceptance updates the baseline for future comparisons.
- Deny a change when it is a regression. The change is marked denied and the build fails; fix the code and run a new build to evaluate the correction.
Chromatic’s documentation puts the intentional-change decision plainly: “If the changes are intentional, press the accept button to update the baselines.” See In pull request workflow.
Get stakeholder sign-off in UI Review
- Open the UI Review attached to the pull or merge request and inspect its Changeset. It compares the head branch with the base branch to show what would change on merge.
- Assign collaborators as reviewers from the Review Activity screen. Assigned reviewers receive an email link. To set reviewers by default, use the project’s Manage page; assigned default reviewers must approve for the Review to pass.
- Leave a discussion on the relevant change if clarification or a revision is needed. Resolve the discussion after the request has been addressed.
- Approve the Review once the changeset is acceptable and required discussions and reviewer approvals are complete. The checklist tracks changeset approval, resolved discussions, and approvals from assigned reviewers.
See Chromatic’s Review documentation for the review workflow and reviewer assignment details.
Make the appropriate status check required
If the repository should block merging until Chromatic reports a result, configure the appropriate status check as required in your Git provider’s branch-protection settings. Require UI Tests when the gate is test status; require UI Review when the gate is stakeholder feedback and sign-off. Chromatic explains the setup and conditions in Mandatory PR checks.
A required check is only useful when the project and CI actually report it. If a check remains pending indefinitely, verify that it is enabled in Chromatic project settings and that the relevant CI step runs. A build run with --skip is marked skipped and passes immediately, even when the commit has visual changes; account for that behavior in your merge policy.
Understand automated and manual reviews
Reviews linked to pull requests
With linked GitHub, GitLab, or Bitbucket integrations, Chromatic can trigger UI Reviews for pull or merge requests. Chromatic documents an exception for GitHub Enterprise Server: opening a pull request does not itself trigger a Review, though one is created when a build runs on the pull-request branch. See the automatic UI Review FAQ.
Manual branch comparison
You can create a manual UI Review to compare branches without a linked Git provider, provided each branch has a build. A manual review does not automatically create a Git-provider status check. Chromatic notes that a custom webhook is a possible way to create one. See Manual UI Review.
Check what a green CI result actually means
A passing job is not necessarily evidence that a person reviewed the snapshots or that changes were accepted. In GitHub Actions, exitZeroOnChanges can let the action exit successfully when it finds changes without accepting them; autoAcceptChanges accepts detected changes. Inspect the configured option before treating a green job as human sign-off. Chromatic also recommends running its step on push events and documents potential unexpected baseline behavior with GitHub’s pull_request event in some configurations. Details are in Chromatic’s GitHub Actions documentation and CI documentation.
Rank #4
Or skip the browser setup:
If you need a screenshot for a separate visual check or workflow, ScreenshotNeo takes one with a GET request:
Quick Recap
Best Value
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. Cookie banners are accepted and removed before the shot, along with known newsletter popups and chat widgets. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed. An MCP server lets AI agents use screenshot tools, and the free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for free and get 1,000 screenshots a month with no card.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
