/explore
|
You are here 
|
mikulskibartosz.name | ||
| | | | |
www.internalpointers.com
A quick and easy way powered by git rebase. |
|
| | | | | ||
| | | | |
williamdurand.fr
My git workflow involves creating a lot of short-lived branches (a.k.a. feature branches), switching between them and, sometimes, I need to rebase one of these branches. git rebase is a super useful git command and I recommend everyone to get more familiar with it (take a look at git rebase in depth for instance). |
|
| | | | | ||
| | | | |
mislav.net
How to settle on whether to merge or rebase at specific points in a team-shared git workflow. |
|
| | | | | ||
| | | | |
citizen428.net
I originally wrote this article for Codementor in October 2014. It should have something for everyone, from fairly new git users to experienced developers. 1. Discard local file modifications Sometimes the best way to get a feel for a problem is diving in and playing around with the code. Unfortunately, the changes made in the process sometimes turn out to be less than optimal, in which case reverting the file to its original state can be the fastest and easiest solution: |
|
| | | |||
