My biggest issue with rebasing is squashing commits can render git bisect useless for determining which particular change a bug was introduced. If you have 50 c

My biggest issue with rebasing is squashing commits can render git bisect useless for determining which particular change a bug was introduced. If you have 50 commits on a feature branch squashed down to 1, all I know is that your branch broke it, not how. I don't need git bisect that often, but when I do, it's a life-saver. That said, I totally endorse squashing small commits to generate a coherent commit - e.g., commit A has broken code in it, commit B fixes that, definitely squash those into C so that if I check out that commit when bug hunting, it compiles.