Explore >> Select a destination
|
You are here 
|
blog.gitbutler.com | ||
| | | | |
vladimirzdrazil.com
|
|
| | | | | A collection of Git tips and tricks you might not know. | |
| | | | |
www.maxpou.fr
|
|
| | | | | Boost your Git efficiency! A simple config for a smoother workflow. | |
| | | | |
www.brandonpugh.com
|
|
| | | | | If you've ever worked on a project with me then I've probably recommended at least one of these config settings in git. git config --global pull.rebase true - tells git to always pull with rebase instead of merge (the equivalent of pull --rebase). This not only saves you having to type the flag every time, but also ensures gui clients will also use rebase when pulling. Note: You should only enable this if you're comfortable with rebasing. | |
| | | | |
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: | ||
