-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Goreleaser #133
Goreleaser #133
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should save those instructions as a template somewhere instead. They probably apply in a similar fashion in more places
1. Ensure local `master` branch is up to date with `origin/master`: | ||
|
||
```sh | ||
git fetch --tags && git pull --tags |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
git fetch --tags && git pull --tags | |
git fetch --all --tags --prune && git pull --tags |
|
||
```sh | ||
git tag vX.Y.Z | ||
git push --tags |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
git push --tags | |
git push | |
git push --tags |
we want to make sure the commit is on the branch
go-makefile-maker adds the required instructions to generate release-info to the GoReleaser workflow, there is no need for a Makefile rule.
and remove explicit `arch` definition for platform.
Do not merge before sapcc/go-makefile-maker#122
FYI @SuperSandro2000 @VoigtS