Title: I&#x27;ve long been in the practice of &quot;commit early, commit often&quot;.  If one use case works I commit, if the unit tests pass I commit. The code may be a mess, the variables may have names like &#x27;foo&#x27; and &#x27;bar&#x27; but I commit to have a last known good state.  If I start mass refactoring and break the unit tests, I can revert everything and start over.<p>I also push often because I&#x27;m forever aware disks can fail.  I&#x27;m not leaving a day&#x27;s worth of work on my local drive and hoping it&#x27;s there the next morning.<p>I&#x27;ve become increasingly aware that my coworkers have nice clean commit histories.  When I look at their PRs, there are 2-4 commits and each is a clean, completely functioning feature.  No &quot;fix misspellings and whitespace&quot; comments.<p>What flow do you follow?
Upvote: