I often don&#x27;t want to record my development history in the master branch because it&#x27;s messy. Instead I squash my work into a single cohesive commit with a decently well written commit message.<p>I&#x27;m not convinced that more commits generally make it easier to understand why code changed. Often when I blame a line, if I see it was changed by a cohesive feature commit, that tells me all I need to know—and if something&#x27;s wrong with it, I can say &quot;hey Joe, you broke the frobber when you implemented the new gizmo.&quot;