You are here |
nvie.com | ||
| | | |
www.cheehow.dev
|
|
| | | | Simple Git branching strategy for small teams. | |
| | | |
www.elidedbranches.com
|
|
| | | | Technology, startups, programming, technical management and software architecture | |
| | | |
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 ... | |
| | | |
stenbrinke.nl
|
|
| | This post introduces my Readme Auto Open project, which helps teams onboard faster by automatically opening README files in VSCode! |