Explore >> Select a destination
|
You are here 
|
nvie.com | ||
| | | | |
raphael.medaer.me
|
|
| | | | | A decade ago, Vincent Driessen wrote a post named "A successful Git branching model". In his post he presents a development model using many Git branches (master, develop, ...) well known as the Git flow. Even if I'm not doing professional development for ten years, I got the opportunity to experiment Git flows in many development teams. As explained by his "Note of reflection (March 5, 2020)", you should not treat this flow as a dogma or panacea. While the flow I will describe in the following lines is ... | |
| | | | |
williamdurand.fr
|
|
| | | | | We all probably know this successful Git branching model, which looks like a very interesting model for teams that want to use Git. That being said, this model is a bit too complex for common needs in my opinion. In this article, I introduce my lightweight model. | |
| | | | |
www.elidedbranches.com
|
|
| | | | | Technology, startups, programming, technical management and software architecture | |
| | | | |
danielkummer.github.io
|
|
| | | |||
