Hacker News new | ask | show | jobs
by dagelf 505 days ago
TL;DR Lazy compute intensive way to find what non-commit change broke your tests... if your tests are any good.
2 comments
daveguy 505 days ago
Lazy, or just the value of human time prioritied over the value of computer time?

I'd rather use git bisect over checking a whole bunch of possibilities manually.

link
aoeusnth1 503 days ago
Is CI and presubmit testing lazy?
link