Explore >> Select a destination
|
You are here 
|
bendauphinee.com | ||
| | | | |
etodd.io
|
|
| | | | | ||
| | | | |
www.janmeppe.com
|
|
| | | | | You're coding. You're in the flow. You're banging code out at the speed of light. You're building the software that is going to change the world. You git add and git commit. You're on fire. You're unstoppable. You're hackerman. | |
| | | | |
www.jtolio.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 ... | ||
