go/goreleaser
go/goreleaser
1
0
Fork 0
mirror of https://github.com/goreleaser/goreleaser.git synced 2025-01-24 04:16:27 +02:00
Code Issues Releases Activity
goreleaser/www/docs/errors/multiple-tokens.md
Carlos Alexandro Becker bb170f3b9c
docs: better document multiple tokens error (#3438) 
closes #3361
2022-10-05 10:27:02 -03:00

1.0 KiB
Raw Blame History

Multiple tokens found, but only one is allowed

GoReleaser infers if you are using GitHub, GitLab or Gitea by which tokens are provided. If you have multiple tokens set, you'll get this error.

Here's an example:

   ⨯ release failed after 0.02s error=gmultiple tokens found, but only one is allowed: GITHUB_TOKEN, GITLAB_TOKEN

Learn more at https://goreleaser.com/errors/multiple-tokens

In this case, you either unset GITHUB_TOKEN or GITLAB_TOKEN. You can read more about it in the SCM docs.

This can also happen if you load the tokens from files. The default paths are:

  • ~/.config/goreleaser/github_token
  • ~/.config/goreleaser/gitlab_token
  • ~/.config/goreleaser/gitea_token

If you have more than one of these files, but for a particular project, you want to force one of them, you can explicitly disable the others by setting them to a file you know won't exist:


# .goreleaser.yaml
env_files:
  gitlab_token: ~/nope
  gitea_token: ~/nope

This will prevent using both GitLab and Gitea tokens.