Hey Jeroen, thanks for reading and responding. I’m not sure what the issue is with thinking every time you commit a change while developing.

I routinely write 10–50 words for each and every commit, and I try to make my commits atomic — fixing only one file or issue at a time.

An Advice for Developers: “Great Git Commit Messages Are Not Shorter Than 50 Characters”

While some other commenters have pointed out that squashing is a good way to remove the “temp commit” and “EOD marker” messages from our git histories, I don’t use crappy commit messages, ever.

Personally, I’d rather have a “bugfix(Predictions): WIP fix the predictions logic to handle the use case where a user has mis-configured their personal settings” if I absolutely need to save work that’s unfinished.