Yes. It is very helpful for seeing what change introduced a bug to help understand why it happened, what could be undone by simple fixes and what assumptions we

Yes. It is very helpful for seeing what change introduced a bug to help understand why it happened, what could be undone by simple fixes and what assumptions were broken. If you use a simple merging workflow --first-parent can avoid testing inside feature branches if you find they are commonly broken. You can also just skip broken commits if they are rare. Also I thought git bisect prefered testing merges before inside the merged branch, but I can't find official documentation in this on my phone. Either way I have never seen this to be much of a problem. (Including in nixpkgs which merges branches every which way)