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.
On GitHub Actions your builds can authenticate to Snapvisor without setting an ARGOS_TOKEN at all — no long-lived secret to store or rotate.
How it works
When a build runs inside a GitHub Actions workflow on a connected repository, Snapvisor can trust the workflow's context to authorize the upload. You leave ARGOS_TOKEN unset and the build is associated with the right project automatically.
Requirements
- The project must be connected to its GitHub repository — connect it first, then the tokenless option becomes available.
- The build has to run in that repository's GitHub Actions, not a fork or an unrelated CI provider.
Requiring an explicit token
Tokenless authentication is a per-project switch. Disable it if you want every CI run to set a project token explicitly — for example to keep a uniform auth path across GitHub Actions and other providers.
For a middle ground that still avoids a static secret, use short-lived GitHub OIDC tokens.
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.
GitHub Actions OIDC authentication
Authenticate GitHub Actions builds to Snapvisor with short-lived OpenID Connect tokens instead of a long-lived project token.