go/goreleaser
go/goreleaser
1
0
Fork 0
mirror of https://github.com/goreleaser/goreleaser.git synced 2025-01-16 03:52:12 +02:00
Code Issues Releases Activity

docs: ref fixes

Browse Source 
refs #3152

Signed-off-by: Carlos A Becker <caarlos0@users.noreply.github.com>
This commit is contained in:
Carlos A Becker 2022-06-10 23:07:21 -03:00
parent 176336f264
commit 1a8e075e4f
No known key found for this signature in database
GPG Key ID: E61E2F7DC14AB940
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
www/docs/cookbooks/build-go-modules.md
View File

@ -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

4
www/docs/customization/env.md
View File

@ -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.