I recommended avoiding Gitflow back in 2018: > There are more complicated systems for branching like Git flow that have a separate “develop” branch and disting

I recommended avoiding Gitflow back in 2018: > There are more complicated systems for branching like Git flow that have a separate “develop” branch and distinguish between “features” and “hot fixes”. These systems are fine if they fit your use case, but if a project releases code quickly, the level of complexity involved in Git Flow is unnecessary. > Ideally, branches should be short lived. One strategy to allow merging a branch before a large feature is fully completed is to create a feature flag that lets the production system have the new code in it but in an inactive state. https://blog.carlmjohnson.net/post/2018/git-gud/ https://blog.carlmjohnson.net/post/2018/git-gud/