Skip to content

fix: clarify how baseline build is chosen #156

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 14, 2025
Merged

fix: clarify how baseline build is chosen #156

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion docs/learn/baseline-build.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,12 @@ A **baseline build** serves as the reference point for comparing screenshots to

## How does Argos determine the baseline build?

Argos uses your Git commit history to identify the most recent successful build on the **baseline branch** (default branch or custom-configured branch). This build is then set as the baseline for screenshot comparisons.
Argos selects the baseline build by finding the most recent **candidate build** that meets all of the following conditions:

- Has the same build name as the triggered build
- All framework tests passed
- Be auto-approved, manually approved or orphan
- Its commit is an ancestor of the merge base between the triggered build's commit and the baseline branch

## What is the baseline branch?

Expand Down