Ask questionsMigrate off of git-flow
The git-flow strategy of hiding our mainline in a
develop branch, and having
master reflect the most stable release made sense in a pre-Go-modules world. Now that most projects have adopted Go modules, I don't think we need to protect them from accidentally installing the mainline branch. Other benefits may include:
I propose we switch to the regular GitHub flow that everyone is used to, and update CONTRIBUTING.md to reflect that.
Let me know if this would break any existing workflows.
Answer questions jhillyerd
@requaos good because I was planning to implement tonight! :)
Related questionsNo questions were found.