Some kind of commit message is useful. When I'm figuring out which point from this morning I want to roll back to, having them tagged as "blah" or "wtf is this?

Some kind of commit message is useful. When I'm figuring out which point from this morning I want to roll back to, having them tagged as "blah" or "wtf is this?" helps. But they're absolutely not worth spending a lot of time on. Write something and move on. I still commit a lot less than I should, and regularly regret not having committed, because I spent 4 years working at a place that required meaningful commit messages and that trained me out of committing early and often. Don't be that guy. But definitely don't squash on merge. You lose all the advantages of git; you can't pull from other people's branches because their commits are going away, you can't automated bisect because you'll just land on your squashes. If you're going to squash then why even bother using git?