Re:Git pull --rebase until it hurts
by plorkyeran on Tuesday April 30, 2013 @09:13AM
(#5631931)
What's worse than all the worthless merge commits is merge commits with actual functional changes introduces while resolving merge conflicts, but still with just the default merge commit message.
> if you have upwards of 20 or so developers constantly doing a pull without a rebase
Or 2 developers; it's still just as annoying. As long as you and the other developer are working at the same time you'll have almost as many merges.
So, sure, falling back to the merge when things went wrong is ok and all, but odds are high you should go ahead and relook at all of your commits anyway. (Another thing, doesn't the rebase keep the initial author date? It isn't like the history is completely fabricated at this point.)
Of course, I'm a big fan of git rebase -i to do some basic cleanup of your commits before pushing. Leave an excessive amount of log messages in? Rebase them out. Neglect basic documentation since you weren't sure if things were going to change? Rebase them in. Sure, I can sympathise with the "you are messing with history" argument, but I find it challenging to believe that I actually care that you commented last. Or that you actually had a few extra helper classes at some point. etc.