mirror of
https://github.com/goreleaser/goreleaser.git
synced 2025-01-04 03:11:55 +02:00
docs: reference --clean instead of --rm-dist everywhere
Signed-off-by: Carlos A Becker <caarlos0@users.noreply.github.com>
This commit is contained in:
parent
9b462fedf3
commit
53fdcd7709
@ -45,7 +45,7 @@ jobs:
|
||||
# either 'goreleaser' (default) or 'goreleaser-pro':
|
||||
distribution: goreleaser
|
||||
version: latest
|
||||
args: release --rm-dist
|
||||
args: release --clean
|
||||
env:
|
||||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||
# Your GoReleaser Pro key, if you are using the 'goreleaser-pro'
|
||||
@ -97,7 +97,7 @@ the [Import GPG][import-gpg] GitHub Action along with this one:
|
||||
uses: goreleaser/goreleaser-action@v4
|
||||
with:
|
||||
version: latest
|
||||
args: release --rm-dist
|
||||
args: release --clean
|
||||
env:
|
||||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||
GPG_FINGERPRINT: ${{ steps.import_gpg.outputs.fingerprint }}
|
||||
@ -179,7 +179,7 @@ step will look like this:
|
||||
uses: goreleaser/goreleaser-action@v4
|
||||
with:
|
||||
version: latest
|
||||
args: release --rm-dist
|
||||
args: release --clean
|
||||
env:
|
||||
GITHUB_TOKEN: ${{ secrets.GH_PAT }}
|
||||
```
|
||||
|
@ -31,7 +31,7 @@ steps:
|
||||
stage: release
|
||||
image: 'goreleaser/goreleaser'
|
||||
commands:
|
||||
- goreleaser --rm-dist
|
||||
- goreleaser --clean
|
||||
```
|
||||
|
||||
You need to pass the variable `GITHUB_TOKEN` in the Codefresh UI that
|
||||
|
@ -45,7 +45,7 @@ release:
|
||||
# generate a changelog.
|
||||
GIT_DEPTH: 0
|
||||
script:
|
||||
- goreleaser release --rm-dist
|
||||
- goreleaser release --clean
|
||||
```
|
||||
|
||||
Notice that `entrypoint` is intentionally blank. See the
|
||||
@ -99,7 +99,7 @@ release:
|
||||
-v /var/run/docker.sock:/var/run/docker.sock \
|
||||
-e DOCKER_USERNAME -e DOCKER_PASSWORD -e DOCKER_REGISTRY \
|
||||
-e GITLAB_TOKEN \
|
||||
goreleaser/goreleaser release --rm-dist
|
||||
goreleaser/goreleaser release --clean
|
||||
```
|
||||
|
||||
In GitLab CI settings, add variables for `DOCKER_REGISTRY`, `DOCKER_USERNAME`,
|
||||
|
@ -33,7 +33,7 @@ Action like the following:
|
||||
with:
|
||||
distribution: goreleaser
|
||||
version: latest
|
||||
args: release --rm-dist
|
||||
args: release --clean
|
||||
env:
|
||||
REGISTRY: ${{ env.REGISTRY }}
|
||||
IMAGE: ${{ env.IMAGE_NAME }}
|
||||
|
@ -10,7 +10,7 @@ You can, though, leverage other tools to do the work for you, like for example
|
||||
```bash
|
||||
git tag "$(svu next)"
|
||||
git push --tags
|
||||
goreleaser --rm-dist
|
||||
goreleaser --clean
|
||||
```
|
||||
|
||||
## Example: semantic-release
|
||||
@ -27,7 +27,7 @@ plugins:
|
||||
- - "@semantic-release/exec"
|
||||
- publishCmd: |
|
||||
echo "${nextRelease.notes}" > /tmp/release-notes.md
|
||||
goreleaser release --release-notes /tmp/release-notes.md --rm-dist
|
||||
goreleaser release --release-notes /tmp/release-notes.md --clean
|
||||
```
|
||||
|
||||
```bash
|
||||
|
@ -33,7 +33,7 @@ monorepo:
|
||||
Then, you can release with (from the project's root directory):
|
||||
|
||||
```bash
|
||||
goreleaser release --rm-dist -f ./subproj1/.goreleaser.yaml
|
||||
goreleaser release --clean -f ./subproj1/.goreleaser.yaml
|
||||
```
|
||||
|
||||
Then, the following is different from a "regular" run:
|
||||
@ -69,7 +69,7 @@ monorepo:
|
||||
Then, you can release with:
|
||||
|
||||
```bash
|
||||
goreleaser release --rm-dist
|
||||
goreleaser release --clean
|
||||
```
|
||||
|
||||
GoReleaser will then ignore the tags that are not prefixed with `v`, and it
|
||||
|
@ -19,9 +19,9 @@ This feature can help in some areas:
|
||||
You don't really need to set anything up. To get started, run:
|
||||
|
||||
```bash
|
||||
goreleaser release --rm-dist --split
|
||||
GOOS=darwin goreleaser release --rm-dist --split
|
||||
GGOOS=windows goreleaser release --rm-dist --split
|
||||
goreleaser release --clean --split
|
||||
GOOS=darwin goreleaser release --clean --split
|
||||
GGOOS=windows goreleaser release --clean --split
|
||||
```
|
||||
|
||||
Note that this step will push your Docker images as well.
|
||||
|
@ -74,7 +74,7 @@ would be nice to have your opinion [here][rlcp-discuss].
|
||||
|
||||
If you want to make sure your releases will keep working properly, you can
|
||||
enable this option and test it out with
|
||||
`goreleaser release --snapshot --rm-dist`.
|
||||
`goreleaser release --snapshot --clean`.
|
||||
|
||||
=== "After"
|
||||
``` yaml
|
||||
|
@ -170,7 +170,7 @@ Use it for testing out new features only.
|
||||
=== "Pro"
|
||||
```bash
|
||||
curl -sfL https://goreleaser.com/static/run |
|
||||
VERSION=nightly DISTRIBUTION=pro bash -s -- release --rm-dist
|
||||
VERSION=nightly DISTRIBUTION=pro bash -s -- release --clean
|
||||
```
|
||||
|
||||
#### docker
|
||||
|
@ -27,7 +27,7 @@ goreleaser init
|
||||
Now, lets run a "local-only" release to see if it works using the [release](/cmd/goreleaser_release/) command:
|
||||
|
||||
```sh
|
||||
goreleaser release --snapshot --rm-dist
|
||||
goreleaser release --snapshot --clean
|
||||
```
|
||||
|
||||
At this point, you can [customize](/customization/) the generated `.goreleaser.yaml` or leave it as-is, it's up to you.
|
||||
|
Loading…
Reference in New Issue
Block a user