News for hackers. Stuff that matters.
Re:The Git history command deserves more attention by locknitpicker on Tuesday July 14, 2026 @09:11AM (#48906317)
> How would you identify the commit that broke the test?

You're asking how to use bisect.

You start with a range of commits you picked. All that bisect does is help you search for a commit within that range that introduces a regression. The responsibility to specify which commits you cover is yours, not the tool.

Re:The Git history command deserves more attention by assbuttbuttass on Tuesday July 14, 2026 @09:18AM (#48906411)
And then bisect fails because it finds one of the many commits that broke the test before the actual regression
Re:The Git history command deserves more attention by locknitpicker on Wednesday July 15, 2026 @01:23AM (#48916583)
> And then bisect fails because it finds one of the many commits that broke the test before the actual regression

And that's ok. You skip the commit and move on with your life.