Recently at work there’s been a number of discussions involving implementing git and what workflow to use, and how they work.
I’ve always defined the workflow we tend to follow as GitFlow-esque. Somewhat like GitFlow in philosophy but not following as strictly. One of the opponents of adopting GitFlow cited the following post GitFlow considered harmful which describes where GitFlow can go wrong, or be overly complex. Interestingly those are the bits that we don’t adopt which makes up the “esque”. Before now though I hadn’t read of a proper description of the workflow we usually follow, luckily an update made in 2017 describes OneFlow workflow.