Explore >> Select a destination
|
You are here 
|
cbea.ms | ||
| | | | |
jiby.tech
|
|
| | | | | Every now and then, at work, I find myself discussing git worfklows, commit messages, branching, releasing, versioning, changelogs etc. Since my opinion has remained fairly consistent for the past few years, I found myself repeating the same points a lot, so I wrote it down. This page is the resulting compilation of my opinions on the software development lifecycle (SDLC), without workplace-specific tangeants. The article is broken down into ideas + recommendations, with recommendations in bold. | |
| | | | |
ejpcmac.net
|
|
| | | | | ||
| | | | |
blog.dnsimple.com
|
|
| | | | | A retrospective of the last two years where we adopted --squash as our default merge strategy for git branches. | |
| | | | |
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: | ||
