Hacker News new | ask | show | jobs
by efilife 15 days ago
Didn't you mean "dissecting"?

Edit: thanks guys, that's very useful knowledge! Could have saved me many times in the past

3 comments

Nope, `bisect`: https://git-scm.com/docs/git-bisect

Figure out a command to test it, a known-good sha and a known-bad sha, and it will binary search its way through the history to find the commit that introduced the failure.

Check out "man git-bisect".

  man git-bisect