It makes reviews easier, as well as debugging with things like bisect. If you leave commits with typos or syntax errors in your master branch history, determin

It makes reviews easier, as well as debugging with things like bisect. If you leave commits with typos or syntax errors in your master branch history, determining weather a commit is good or bad for the right reason becomes a much more arduous task. If you do a rebase + squash on merge approach, the commit history is succinct, descriptive, and healthy, which I’ve found immensely beneficial. (Disclosure: I currently work at GitHub, but these opinions are my own)