1
0
mirror of https://github.com/goreleaser/goreleaser.git synced 2025-03-17 20:47:50 +02:00

docs: fix internal links that result in a broken navigation sidebar (#1909)

I suspect this is something about the mkdocs template, but I'm not familiar enough, and this is easy.
This commit is contained in:
Ben Sandberg 2020-11-19 12:31:26 -08:00 committed by GitHub
parent f417d7783d
commit 9a19dee300
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
16 changed files with 21 additions and 21 deletions

View File

@ -76,7 +76,7 @@ archives:
```
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).
!!! tip
You can add entire folders, its subfolders and files by using the glob notation,

View File

@ -64,7 +64,7 @@ blobs:
```
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).
## Authentication

View File

@ -127,7 +127,7 @@ builds:
```
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).
Here is an example with multiple binaries:
@ -219,7 +219,7 @@ builds:
- second-script.sh
```
All properties of a hook (`cmd`, `dir` and `env`) support [templating](/customization/templates)
All properties of a hook (`cmd`, `dir` and `env`) support [templating](/customization/templates/)
with `post` hooks having binary artifact available (as these run _after_ the build).
Additionally the following build details are exposed to both `pre` and `post` hooks:

View File

@ -25,4 +25,4 @@ checksum:
```
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).

View File

@ -14,7 +14,7 @@ If you have only one `build` setup,
the configuration is as easy as adding the
name of your image to your `.goreleaser.yml` file:
The docker image declaration supports templating. Learn more about the [name template engine](/customization/templates).
The docker image declaration supports templating. Learn more about the [name template engine](/customization/templates/).
```yaml
dockers:
@ -103,7 +103,7 @@ dockers:
```
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).
These settings should allow you to generate multiple Docker images,
for example, using multiple `FROM` statements,
@ -130,7 +130,7 @@ This will build and public the following images:
- `myuser/foo`
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).
## Keeping docker images updated for current major
@ -162,7 +162,7 @@ With these settings you can hopefully push several different docker images
with multiple tags.
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).
## Publishing to multiple docker registries
@ -220,4 +220,4 @@ docker build -t myuser/myimage . \
```
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).

View File

@ -130,7 +130,7 @@ brews:
```
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).
By defining the `brew` section, GoReleaser will take care of publishing the
Homebrew tap.

View File

@ -27,4 +27,4 @@ to do things that are more complex than just calling a command with some
attributes, wrap it in a shell script or into your `Makefile`.
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).

View File

@ -32,4 +32,4 @@ milestones:
```
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).

View File

@ -261,4 +261,4 @@ nfpms:
```
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).

View File

@ -107,4 +107,4 @@ These settings should allow you to push your artifacts to any number of endpoint
which may require non-trivial authentication or has otherwise complex requirements.
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).

View File

@ -144,7 +144,7 @@ ALLOWED_TYPES = application/gzip|application/x-gzip|application/x-gtar|applicati
`draft` and `prerelease` are only supported by GitHub and Gitea.
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).
## Customize the changelog

View File

@ -146,7 +146,7 @@ snapcrafts:
```
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).
!!! note
GoReleaser will not install `snapcraft` nor any of its dependencies for you.

View File

@ -29,7 +29,7 @@ This means that if you use `{{ .Version }}` on your name templates, you'll
get the snapshot version.
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).
Note that the idea behind GoReleaser's snapshots if mostly for local builds
or to validate your build on the CI pipeline. Artifacts shouldn't be uploaded

View File

@ -23,4 +23,4 @@ source:
```
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).

View File

@ -179,4 +179,4 @@ uploads:
These settings should allow you to push your artifacts into multiple HTTP servers.
!!! tip
Learn more about the [name template engine](/customization/templates).
Learn more about the [name template engine](/customization/templates/).

View File

@ -7,6 +7,6 @@ GoReleaser enforces semantic versioning and will error on non compliant tags.
Your tag **should** be a valid [semantic version](http://semver.org/).
If it is not, GoReleaser will error.
The `v` prefix is not mandatory. You can check the [templating](/customization/templates)
The `v` prefix is not mandatory. You can check the [templating](/customization/templates/)
documentation to see how to use the tag or each part of the semantic version
in name templates.