Explore >> Select a destination
|
You are here 
|
techblog.izotope.com | ||
| | | | |
ryanharter.com
|
|
| | | | | I recently shared how I use Git to automatically track my versions. There's quite a bit more to my git workflow than just tagging versions, though, so I'd like to dive into my git usage just a little more. One of my clients introduced me to a very popular, and useful, git branching strategy commonly called Git-Flow based on Vincent Driessen's branching model. I highly recommend reading his article, it's quite good and describes a very useful branching model. | |
| | | | |
truss.works
|
|
| | | | | A git workflow that supports feature development isolation, continuous deployment, and has minimal overhead when performing common operations like branching and merging | |
| | | | |
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. | |
| | | | |
danielkummer.github.io
|
|
| | | |||
