Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Having a well curated one-logical-change-per-commit history is incredibly valuable when bisecting a regression.


Didn't you mean "dissecting"?

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


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




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: