Percy Developer Hub

Welcome to the Percy Developer Hub. You'll find comprehensive guides and documentation to help you start working with Percy as quickly as possible, as well as support if you get stuck. Let's jump right in!

Approval workflows

Covered in this doc

Different kinds of snapshot approvals in Percy
How auto-approved branches work
How approval carryforward works

Percy's approval workflow is an important part of the visual review process.

Types of approvals


Within Percy, you can either "Approve All" snapshots in an entire build, approve groups of matching visual changes or approve individual snapshots.

Once all snapshots in a build are approved, the whole build will be approved. If you have a source code integration installed, only marking a complete build as approved will mark your Percy check as "passed."

Auto-approved branches


This project setting allows teams to filter and ‘auto-approve’ specific branches.

Branches that meet the specified filter(s) don’t require manual approval and will always be ‘green,’ reducing false positives and saving your team time.

By default, commits on master are marked as Auto-approved.

Approval carryforward


Previously approved snapshots will stay approved from one build to the next for the life of the branch. In other words, snapshots are "carried forward" so identical snapshots will only have to be approved once per branch. Read more about our base build selection logic.

Approval workflows


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.