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
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.
Only team admins can configure the GitLab connection. If you're not an admin, ask your team owner to set it up.
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
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.
GitHub
Connect Snapvisor to GitHub for build status checks on your pull requests, including a light install that works without read access to your code.
GitHub tokenless authentication
Let GitHub Actions upload to Snapvisor without an ARGOS_TOKEN environment variable. Learn how tokenless authentication works and when to disable it.