-
Notifications
You must be signed in to change notification settings - Fork 33
Dev Release Workflow
Barnaby Keene edited this page Apr 2, 2020
·
1 revision
- Roughly Git-flow.
- Build in feature-branches
-
Squash Merge from feature branches to
dev -
Merge Commit from
devtomaster - ^ Very important for not screwing up future PRs by diverging the histories. Makes the GitHub UI break.
Once merged to master, checkout master locally and pull, run git tag <next version> (note that versions for sampctl do not have a v prefixing them) then git push --tags and GoReleaser should do the rest via TravisCI.