You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/learn/integrations/github.mdx
+51-17Lines changed: 51 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,27 +7,34 @@ description: Connect Argos to GitHub for automated visual testing on pull reques
7
7
8
8
# GitHub Integration
9
9
10
-
Seamlessly integrate Argos with GitHub for automated visual testing directly within your workflow. Connect Argos to your repositories and receive instant feedback on your pull requests, making it easier to maintain visual consistency across your project.
10
+
Connect Argos to GitHub for automated visual testing on every pull request and merge queue run. Argos reads commit history to pick the right baseline build and reports results back to GitHub so you can ship with confidence.
11
+
12
+
## What Argos does on GitHub
13
+
14
+
- Add commit and pull request checks, so Argos results can block merges when required in GitHub.
15
+
- Post [pull request comments](/pull-request-comments) with the latest build results and links back to Argos.
16
+
- Analyze commit history to find the right merge base and select the correct [baseline build](/baseline-build) for visual comparisons.
11
17
12
18
## Why Argos needs repository access
13
19
14
20
Argos analyzes commit history to choose the right [baseline build](/baseline-build) and posts commit statuses or pull request comments. Granting repository access lets Argos read commits, find merge bases, and report build results back to GitHub.
15
21
16
-
## GitHub Connect
22
+
## Choose your access level
17
23
18
-
Use GitHub Connect to log in to Argos with your GitHub account. This integration allows Argos to access your repositories and streamline the setup process.
24
+
-**Full access (recommended)** — Required for Merge Queue and baseline selection based on commit history.
25
+
-**Limited access (no content)** — Works for basic checks without reading repository content; Merge Queue is not supported. See [GitHub Integration without Content Permission](#github-integration-without-content-permission).
19
26
20
-
## Argos' GitHub App
27
+
Use GitHub Connect to log in with your GitHub account, then install the Argos GitHub App to link repositories.
21
28
22
-
Argos provides a dedicated GitHub App that connects directly to your repositories, enabling real-time visual testing feedback on pull requests.
29
+
## Install the Argos GitHub App
23
30
24
-
### Install the Argos GitHub App
31
+
Argos provides a dedicated GitHub App that connects directly to your repositories, enabling real-time visual testing feedback on pull requests.
25
32
26
33
1. Visit the [Argos app page on GitHub](https://github.com/apps/argos-ci)
27
34
2. Click on "Configure" and select the organization where you want to install Argos
28
35
3. Follow the prompts to complete the installation
29
36
30
-
### Import a GitHub Repository to Argos
37
+
### Import a GitHub repository to Argos
31
38
32
39
1. Sign in to Argos and click on "Create a new project"
33
40
2. Choose GitHub as your provider, then click "Import your repository"
@@ -51,30 +58,57 @@ Argos needs the following permissions to operate:
51
58
52
59
We take your security and privacy seriously. If you have any concerns or questions, please [contact us](https://argos-ci.com/contact).
53
60
61
+
## GitHub Merge Queue support
62
+
63
+
Argos supports GitHub Merge Queue when you use the full-access Argos GitHub App. Merge Queue relies on Argos reading commit history to compute merge bases and publish required checks, so the restricted “GitHub without content access” integration does not support it. When Argos runs inside the merge queue, it compares your queued change against the previously approved commit on the target branch to ensure only clean visual changes are merged.
64
+
65
+
### GitHub Actions setup for Merge Queue
66
+
67
+
Listen to both `pull_request` and `merge_group` events so Argos uploads run for PR reviews and for queued merges:
68
+
69
+
```yaml title=".github/workflows/ci.yml"
70
+
name: Visual tests
71
+
72
+
on:
73
+
pull_request:
74
+
merge_group:
75
+
76
+
jobs:
77
+
argos:
78
+
runs-on: ubuntu-latest
79
+
steps:
80
+
- uses: actions/checkout@v6
81
+
- uses: actions/setup-node@v6
82
+
- run: npm ci
83
+
- run: npm run test:e2e # Run E2E tests with Argos SDK integration
If you prefer to use Argos without granting full content access to your repositories, you can now integrate via a more restricted setup.
90
+
If you prefer to use Argos without granting full content access to your repositories, you can integrate via a more restricted setup. This mode does not support Merge Queue because Argos cannot read commit history.
57
91
58
92
### Setting Up Argos with Limited GitHub Access
59
93
60
-
1. From the dashboard, select your team from the scope selector
61
-
2. Select the **Settings** tab and go to the **Integrations** section
62
-
3. Scroll to "GitHub without content access"
63
-
4. Click **Install GitHub App**
94
+
1. From the dashboard, select your team from the scope selector.
95
+
2. Select the **Settings** tab and go to the **Integrations** section.
96
+
3. Scroll to "GitHub without content access".
97
+
4. Click **Install GitHub App**.
64
98
65
99

66
100
67
-
3. On the next screen you are redirected to GitHub, choose the specific repositories where you want to install the Argos app
101
+
5. On GitHub, choose the specific repositories where you want to install the Argos app.
68
102
69
103

70
104
71
-
4. Select **Projects** tab
72
-
5. Click **Create a new project** at the top right
73
-
6. Select **Continue with GitHub (no-content access)**
105
+
6. Back in Argos, go to the **Projects** tab.
106
+
7. Click **Create a new project** at the top right.
107
+
8. Select **Continue with GitHub (no-content access)**.
74
108
75
109

0 commit comments