4 ms·

Doesn't squash and rebase eliminate this problem? It removes all those possibly broken intermediate commits once it's in master. I'll add that another annoying

Doesn't squash and rebase eliminate this problem? It removes all those possibly broken intermediate commits once it's in master. I'll add that another annoying thing about rebasing is that if you make multiple changes to the same piece of code that conflict with changes on master, when you rebase, you have to resolve each change independently instead of only the last snapshot. However, if the changes are in different places, I like the incremental conflict resolution process of rebasing instead of the one-shot merge commit.

jmiserez 9y ago
You can have git remember the previous conflict resolutions and automatically apply them the next time you rebase the same code by setting git config --global rerere.enabled true It’s a builtin feature, see the documentation https://git-scm.com/docs/git-rerere https://git-scm.com/docs/git-rerere and a description here: https://git-scm.com/blog/2010/03/08/rerere.html https://git-scm.com/blog/2010/03/08/rerere.html Very handy if you use rebase with multiple commits to the same code.