Explore >> Select a destination
|
You are here 
|
jiby.tech | ||
| | | | |
nvie.com
|
|
| | | | | In this post I present a Git branching strategy for developing and releasing software as I've used it in many of my projects, and which has turned out to be very successful. | |
| | | | |
github.com
|
|
| | | | | OCI Image Format. Contribute to opencontainers/image-spec development by creating an account on GitHub. | |
| | | | |
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 ... | |
| | | | |
johannesbrodwall.com
|
|
| | | |||
