Carlos Alexandro Becker dc6a4e7e2f feat: allow to forcefully use a token when multiple are set (#3910) ... 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>		2023-04-05 16:33:22 -03:00
..
build.md	docs: errors/build	2022-12-04 10:29:02 -03:00
dirty.md	docs: improve git dirty err page	2023-01-30 23:25:23 -03:00
docker-build.md	feat: improve docker errors (#3080)	2022-05-02 22:05:42 -03:00
multiple-binaries-archive.md	docs: archives.*.builds is type []string (#3406)	2022-09-26 12:30:07 -03:00
multiple-tokens.md	feat: allow to forcefully use a token when multiple are set (#3910)	2023-04-05 16:33:22 -03:00
no-history.md	docs: no history	2022-02-01 11:07:28 -03:00
no-main.md	feat: deprecate --rm-dist in favor of new --clean flag (#3702)	2023-01-20 23:47:08 -03:00
release-upload.md	docs: fix list item count (#3816)	2023-03-01 09:46:56 -03:00
resource-not-accessible-by-integration.md	docs: update github-action documentation (#3640)	2022-12-14 12:16:24 -03:00
scoop-archive.md	fix: clarify scoop no windows error (#3894)	2023-03-29 10:18:40 -03:00