Explore >> Select a destination
|
You are here 
|
petelevasseur.com | ||
| | | | |
aaronbos.dev
|
|
| | | | | Git's rebase functionality could be one of the most polarizing features of the ubiquitous version control system. Some have horror stories of rebasing branches, while others use it whenever possible. In this post, we'll be touching on the interactive rebase feature which can reduce a lot of the anxiety around rebasing Git branches. | |
| | | | |
wpsoftware.net
|
|
| | | | | ||
| | | | |
blog.dnsimple.com
|
|
| | | | | A retrospective of the last two years where we adopted --squash as our default merge strategy for git branches. | |
| | | | |
danielpecos.com
|
|
| | | In a previous post, we have seen what Git is and its main characteristics. Now, we'll go more into detail about its functionality and we'll see what a usual day working with Git looks like. But before, some initial concepts: Repository: A working tree of files and directories which can be versioned, keeping track of every single modification made over the working tree, been able to move forward and backward in its history. | ||
