# GitLab merge request statuses

Canonical: https://snapvisor.io/docs/gitlab

> Connect Snapvisor to GitLab with a personal access token so build results appear as commit statuses on your merge requests, including self-managed GitLab.



Set up GitLab so Snapvisor updates commit statuses on your merge requests, the same way it does on GitHub pull requests.

## Connect with an access token [#connect-with-an-access-token]

Snapvisor talks to GitLab using a **personal access token** with repository access. Add it in your team or account settings; Snapvisor uses it to update commit statuses on behalf of the user who created the token, so pick an account that should appear as the status author.

<Callout type="warn">
  Only team admins can configure the GitLab connection. If you're not an admin, ask your team owner to set it up.
</Callout>

## Self-managed GitLab [#self-managed-gitlab]

Running GitLab on your own infrastructure is supported. Configure the GitLab proxy URL for your instance so Snapvisor reaches your self-managed server instead of gitlab.com.

## Importing a project [#importing-a-project]

Once the access token is set up you can import a repository from GitLab and link it to a Snapvisor project. From then on every build posts its result back as a commit status on the matching merge request. The status is named `snapvisor` (`snapvisor/summary` for the summary check) and stays pending until a reviewer approves or rejects the changes.

If a merge request rule or an external check waits on a status named `argos` or `argos/summary`, switch it to `snapvisor` or `snapvisor/summary` before 2026-11-25. Until then Snapvisor keeps posting the old names too, with the same state and a description starting with "deprecated:".

## Running the job [#running-the-job]

The merge request statuses come from builds your pipeline uploads. For the CI job itself, the variables the SDK reads and a working `.gitlab-ci.yml`, see [visual regression testing in GitLab CI](https://snapvisor.io/gitlab-ci). If a build compares against the wrong baseline, check [troubleshooting](/troubleshooting).

