I have good experiences with trunk based development meaning that “master”
(we use “main”) is the main development line and you down-port to release
branches with cherry picking and tags. So as soon as you commit something
which is considered a major change (requiring a new version) then also
appen
Hi All,
I need to release a V2 of my module. (
https://github.com/deepmap/oapi-codegen). I understand what to do on the Go
side in terms of the /v2 suffix and go.mod changes, but I'm a little bit
unclear how this works w.r.t git branches. Yes, I've looked at
https://golang.org/ref/mod#vcs-find
My
