From 1a8e075e4fb9e262ec695723f552f281cad558d8 Mon Sep 17 00:00:00 2001 From: Carlos A Becker Date: Fri, 10 Jun 2022 23:07:21 -0300 Subject: [PATCH] docs: ref fixes refs #3152 Signed-off-by: Carlos A Becker --- www/docs/cookbooks/build-go-modules.md | 2 +- www/docs/customization/env.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/www/docs/cookbooks/build-go-modules.md b/www/docs/cookbooks/build-go-modules.md index 1522627da..2e80f7c0a 100644 --- a/www/docs/cookbooks/build-go-modules.md +++ b/www/docs/cookbooks/build-go-modules.md @@ -100,7 +100,7 @@ Make sure to also read the [relevant documentation][docs] for more options. [issue]: https://github.com/goreleaser/goreleaser/issues/1354 [pr]: https://github.com/goreleaser/goreleaser/pull/2129 -[docs]: /customization/gomod/ +[docs]: /customization/verifiable_builds/ ## Real example diff --git a/www/docs/customization/env.md b/www/docs/customization/env.md index 5381ee992..830d4f965 100644 --- a/www/docs/customization/env.md +++ b/www/docs/customization/env.md @@ -2,7 +2,7 @@ Global environment variables to be passed down to all hooks and builds. -If you have an environment variable named FOOBAR set to "on", your `.goreleaser.yaml` file could use it like this: +If you have an environment variable named `FOOBAR` set to `on`, your `.goreleaser.yaml` file could use it like this: ```yaml # .goreleaser.yaml @@ -16,7 +16,7 @@ builds: - binary: program ``` -This way, both `go mod tidy` and the underlying `go build` will have `FOO` set to `on`. +This way, both your before hooks (in this example, `go mod tidy`) and the underlying builds (using `go build`) will have `FOO` set to `on`. The root `env` section also accepts templates.