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

▲ efilife 2 hours ago | parent [-]

Didn't you mean "dissecting"?

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

	▲	psadauskas 2 hours ago \| parent \| next [-]
		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.
	▲	seba_dos1 2 hours ago \| parent \| prev \| next [-]
		Check out "man git-bisect".
	▲	jolmg 2 hours ago \| parent \| prev [-]
		`man git-bisect`