A git-flow screencast » nvie.com. Getting Started – Git-Flow « Some thoughts, ideas and fun!!! Overview In a previous article called “Getting Started – Git” I explained most of the concepts that you should know about Git.
I also mentioned in that article that I was busy writing another article on how to use Git-Flow as a branching strategy for your Git Repositories. Even though the name for this specific branching strategy is Git-Flow, you could also choose to use it with some of your other Version Control Systems. For the scope of this article I’ll be explaining the concepts introduced in Git-Flow and then I’m going to explain how to use it with Git and GitHub. I’ll be covering the following: A successful Git branching model » nvie.com. Note of reflection (March 5, 2020)This model was conceived in 2010, now more than 10 years ago, and not very long after Git itself came into being.
In those 10 years, git-flow (the branching model laid out in this article) has become hugely popular in many a software team to the point where people have started treating it like a standard of sorts — but unfortunately also as a dogma or panacea.During those 10 years, Git itself has taken the world by a storm, and the most popular type of software that is being developed with Git is shifting more towards web apps — at least in my filter bubble. Web apps are typically continuously delivered, not rolled back, and you don't have to support multiple versions of the software running in the wild.This is not the class of software that I had in mind when I wrote the blog post 10 years ago.
Why git? ¶