+goreleaser --rm-dist
+```
+
+Check the console output to make sure that there are no messages about a failed publish. \
+If all is well you should the git tag on the releases page updated with a ChangeLog and the published binaries.
+
+### How to Publish to Gitea and others
+
+Gitea Token: https://try.gitea.io/user/settings/applications
+
+```yml
+env_files:
+ gitea_token: ~/.config/goreleaser/gitea_token
+gitea_urls:
+ api: https://try.gitea.io/api/v1/
+```
+
+GitLab Token: https://gitlab.com/profile/personal_access_tokens
+
+```yml
+env_files:
+ gitlab_token: ~/.config/goreleaser/gitlab_token
+gitlab_urls:
+ api: https://gitlab.com/api/v1/
+```
+
+Also see https://goreleaser.com/environment/
+
+### How to Build for Raspberry Pi (ARM)
+
+All of the Raspberry Pis are ARM processors and can run Linux. Most can run Windows as well.
+
+- RPi 4 is ARM 64, also known as `aarch64`, `arm64`, and `armv8`.
+- RPi 3 could run `armv7` and `arm64`.
+- RPi 2, RPi Zero, and RPi can run either `armv6` or `armv7`.
+
+To build Go binaries for ARM, you'll need to update the `build` section of your `.goreleases.yml`.
+
+```yml
+builds:
+ - env:
+ - CGO_ENABLED=0
+ goos:
+ - linux
+ - windows
+ - darwin
+ goarch:
+ - 386
+ - amd64
+ - arm
+ - arm64
+ goarm:
+ - 6
+ - 7
+```
+
+For information on other supported build options, such as BSD and ppc, see
+[Go (Golang) GOOS and GOARCH](https://gist.github.com/asukakenji/f15ba7e588ac42795f421b48b8aede63).
+
+### How to Build from the `cmd` Directory
+
+By default GoReleaser assumes that the root of your package is `package main`.
+
+If your `package main` is in a `cmd/` directory or you have multiple commands,
+you should update your `builds` directive accordingly.
+
+```yml
+- builds:
+ - id: command123
+ main: ./cmd/command123/command123.go
+ goos:
+ - linux
+ - windows
+ - darwin
+ goarch:
+ - amd64
+ - arm64
+ - id: other321
+ main: ./cmd/other321/other321.go
+ goos:
+ - linux
+ - windows
+ - darwin
+ goarch:
+ - amd64
+ - arm64