Since we're talking about naming branches, what are your preferred names for branches ? I like 4-letter names: - `main` points to the last release for libraries (along with tags for history) - `prod` points to production in deployable projects (not libraries) - `next` is the development branch for the next version - `deps` is a temporary branch for dependency updates, squashed and merged regularly onto `next`
Good for you that you found something that works for you. But why the random length restrictions to 4 chars, seems kind of outdated? Also, how does using only a "next" branch for development scale for teams (maybe using a fork-based workflow?). While I use a similar approach like yours on my personal projects, I still prefer the widely known and battle proven Git-Flow when working on agile teams: - master - develop (…
I've never managed to find use in the "complexity" added by adhering strictly to GitFlow (maybe I'm working in too small teams), I don't find it suited to the continuous delivery method. I still use feature branches and hotfixes though.
I much prefer a linear history, and use semantic-release to automate releases via commit message standardisation, which gets rid of the `release/*` pattern.