> Your history should be clean and easily readable. Yes so much. I've harped on it a great deal here, but clean history is a big deal, and that does mean lear

> Your history should be clean and easily readable. Yes so much. I've harped on it a great deal here, but clean history is a big deal, and that does mean learning to love rebasing. > Each commit should contain one logical change and ideally pass CI. Well, at least ones that are expected not to pass CI should be labeled so, because it's useful to first push a change to tests that shows there's a bug, then push the fix to that bug.