mirror of
https://github.com/goreleaser/goreleaser.git
synced 2025-03-17 20:47:50 +02:00
docs: fix monorepo.dir prop
Signed-off-by: Carlos Alexandro Becker <caarlos0@gmail.com>
This commit is contained in:
parent
7f0edf6fe0
commit
9ed3c0c4a7
@ -18,7 +18,7 @@ project_name: subproj1
|
||||
|
||||
monorepo:
|
||||
tag_prefix: subproject1/
|
||||
folder: subproj1
|
||||
dir: subproj1
|
||||
```
|
||||
|
||||
Then, you can release with (from the project's root directory):
|
||||
@ -30,11 +30,11 @@ goreleaser release --rm-dist -f ./subproj1/.goreleaser.yml
|
||||
Then, the following is different from a "regular" run:
|
||||
|
||||
- GoReleaser will then look if current commit has a tag prefixed with `subproject1`, and also the previous tag with the same prefix;
|
||||
- Changelog will include only commits that contain changes to files within the `subproj1` folder;
|
||||
- Changelog will include only commits that contain changes to files within the `subproj1` directory;
|
||||
- Release name gets prefixed with `{{ .ProjectName }} ` if empty;
|
||||
- All build's `dir` setting get set to `monorepo.folder` if empty;
|
||||
- All build's `dir` setting get set to `monorepo.dir` if empty;
|
||||
- if yours is not, you might want to change that manually;
|
||||
- Extra files on the release, archives, Docker builds, etc are prefixed with `monorepo.folder`;
|
||||
- Extra files on the release, archives, Docker builds, etc are prefixed with `monorepo.dir`;
|
||||
- On templates, `{{.PrefixedTag}}` will be `monorepo.prefix/tag` (aka the actual tag name), and `{{.Tag}}` has the prefix stripped;
|
||||
|
||||
The rest of the release process should work as usual.
|
||||
|
Loading…
x
Reference in New Issue
Block a user