Monitoring mode
Auto-approve branches so their builds set a success check without manual review. Learn how monitoring mode differs from the CI review workflow in Snapvisor.
Not every branch needs a human to approve each change. Monitoring mode auto-approves builds on branches you trust, so they set their own baseline and report a passing check.
CI mode vs monitoring mode
In the default CI mode a build compares against the approved baseline on your base branch and waits for review. In monitoring mode a build with no prior approval doesn't block — it reports a success check and, once you approve it, becomes the baseline future builds compare against.
Auto-approved branches
Monitoring mode is configured with an auto-approved branches pattern in project settings. Any branch matching the glob is automatically approved and gets a success status check. By default only your default base branch is auto-approved.
main
{main,production}
release/**When to use it
- Production or release branches where the merged state is the source of truth, not something to re-review.
- Continuously monitoring a live app for unexpected visual drift rather than gating pull requests.
Auto-approved builds keep the baseline current for everyone. See Baseline builds for how the reference is resolved.
Baseline builds
The baseline is the last approved build on your base branch. Learn how Snapvisor picks the reference build and resolves the base branch for every comparison.
Parallel testing
Split a screenshot suite across machines and upload each shard as a batch. Learn Snapvisor's automatic and manual parallel finalize modes.