3 ms·
> it can make a bisect take way longer than if just merge commits are tested. The whole beauty of bisect is that is a binary search where if you double the num
by account42 4y ago
> it can make a bisect take way longer than if just merge commits are tested.
The whole beauty of bisect is that is a binary search where if you double the number of commits you only need to do ~1 additional check. So no, it can't take "way" longer.
And it's not like you'd call it a day after finding the merge commit that breaks things - you then need to find the actual problem with that branch and the fastest way to do that is bisecting down to the individual commit so you are actually doing the same work but artificially restricting git bisect from evenly dividing the search space by restricting it to merge commits first.