You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think if Goreleaser is automatically attaching the binaries (a.k.a. artifacts) to the git release/tags, there is no need for binaries to be committed directly to the repository.
Applies to files in dist/ and ghosts in the repository root.
The text was updated successfully, but these errors were encountered:
Goreleaser has documentation and an example repository that makes use of GitHub Actions to create binaries using GitHub's free CI/CD and attaches them to tags as seen here.
Users can then navigate to the most recent tag and download the required binaries.
I think if Goreleaser is automatically attaching the binaries (a.k.a. artifacts) to the git release/tags, there is no need for binaries to be committed directly to the repository.
Applies to files in
dist/
andghosts
in the repository root.The text was updated successfully, but these errors were encountered: