Getting started
First review
Approve your first build so it becomes the baseline.
Open the build from the project page. The build page lists its screenshots grouped by state (changed, added, removed, unchanged) and shows the selected one in a viewer.
Approve the baseline
Section titled “Approve the baseline”- Look through the screenshots. In a first build every one is Added.
- Approve them one by one, or approve the whole build. The build becomes Approved, and it's now the baseline for later builds with the same name.
- Upload the same screenshots again (a re-run). The build finishes with no changes and
circi upload --waitexits0.
Now change a screenshot and upload from a new commit. The build shows that screenshot as changed, with the diff next to the baseline. That is the loop. Reviewing a build covers the build page, shortcuts, comments and requests.
Close the loop with your git host
Section titled “Close the loop with your git host”- Link the project to its repository to get a CirCI check on pull requests with Approve and Reject buttons, and a summary comment: GitHub, GitLab, Bitbucket.
- Mark that check as required in the repository's branch protection to block merges until someone reviews.
- Add Slack or a webhook to hear about builds.
Next steps
Section titled “Next steps”- Tune project settings: threshold, retention, merge gate, flaky handling.
- Set up review rules so the right people are asked.
- Read CI examples for sharded runs and several builds per commit.