3 ms·
> leaving broken commits useless for git bisect. Honestly all of this is just a function of Git’s tooling being pretty bad. There’s no reason that a merge bas
by forrestthewoods 2y ago
> leaving broken commits useless for git bisect.
Honestly all of this is just a function of Git’s tooling being pretty bad.
There’s no reason that a merge based history can’t be presented as a linear history. That’s purely a matter of how the information is displayed!
Similarly there’s absolutely no reason that git bisect should try to operate on every single commit. We live in a world where CI systems need to land a queue commits at a time. No one can afford to run every test on every commit. Git should have support for tagging commits that had varying levels of tests and then running bisect against only those commits. Easy peasy.