4 ms·

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

• efilife 3mo ago
  Didn't you mean "dissecting"? Edit: thanks guys, that's very useful knowledge! Could have saved me many times in the past
  • jolmg 3mo ago
    man git-bisect
  • seba_dos1 3mo ago
    Check out "man git-bisect".
  • psadauskas 3mo ago
    Nope, `bisect`: https://git-scm.com/docs/git-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.