|
You are here |
developerexperience.io | ||
| | | | |
danielkummer.github.io
|
|
| | | | | ||
| | | | |
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. | |
| | | | |
www.bryantwebconsulting.com
|
|
| | | | | A Web Programmer's Exploration: Git Branching Strategy for Web Development | |
| | | | |
andreabergia.com
|
|
| | | Git has an excellent tool designed to help you reorder the commit history: interactive rebase. This can be excellent if you want to keep the history clean, so that it helps other programmers understand the logic behind the changes rather than the actual sequence of commits. Let's walk through an example. Let's write some history Link to heading Let's start by creating an empty project in a new directory: | ||