I use this pattern mostly on solo projects and small OSS libraries, when working with clients in teams there is usually already a convention in place, most ofte

I use this pattern mostly on solo projects and small OSS libraries, when working with clients in teams there is usually already a convention in place, most often just `master` and `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.