&gt; git bisect pointing to the merge commit as culprit is exactly what should happen<p>in theory, maybe. in practice, this simply does not help if you are looking at massive merge commits. sometimes, the merge goes wrong even with no conflicts, and then you can debug that massive merge with little clue where to start.<p>compare that to rebasing, where you have a hopefully small commit that breaks. you indeed loose the information whether the rebase broke it or the initial version was broken as well, but I don&#x27;t see the practical difference, it needs to be fixed either way.