dc6a4e7e2f
This would allow to, when multiple tokens are set in the environment, force which one you want to use. The need for this comes from the fact gitea sets both `GITHUB_TOKEN` and `GITEA_TOKEN`, and doesn't allow to easily disable either. With this, users can add a `GORELEASER_FORCE_TOKEN=gitea` to force the gitea client to be used. I'm not sure what's the best name for this env yet, happy to hear suggestions. Also improved the `env_test.go` file a bit, as it was kinda messy with env vars... refs https://github.com/orgs/goreleaser/discussions/3900 --------- Signed-off-by: Carlos A Becker <caarlos0@users.noreply.github.com>
GoReleaser
Deliver Go binaries as fast and easily as possible.
GoReleaser builds Go binaries for several platforms, creates a GitHub release and then pushes a Homebrew formula to a tap repository. All that wrapped in your favorite CI.
Get GoReleaser
Documentation
Documentation is hosted live at https://goreleaser.com
Community
You have questions, need support and or just want to talk about GoReleaser?
Here are ways to get in touch with the GoReleaser community:
You can find the links above and all others here.
Code of Conduct
This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. We appreciate your contribution. Please refer to our contributing guidelines for further information.
Badges
Sponsors
Does your company use goreleaser? Help keep the project bug-free and feature rich by sponsoring the project.
Backers
Love our work and community? Become a backer.
Contributors
This project exists thanks to all the people who contribute. [Contribute].
Stargazers over time
