Why do people fucking do this? You're working in a team, ffs. Even if right now you're the only one working on that branch or whatever, that doesn't make it okay to have the most useless commit messages of all time.

Because he/she uses git for cloud storage, not vcs.

Merge -> squash and delete branch!

Yeah i usually save it as 'updated' then commit

@C0D4 dont merge, delete branch

We have a commit message policy in the company I work to prevent something like this.

On MY branch I often commit WIP, until a functional military stone where I squash it to have a true commit message.
Also use it when I couldn't finish a task the same day. Or when I config/debug a CI workflow problem as it must go through the CI.

The problem is more : why the commit messages made it into master!

minor

minor

minor

bugfix

minor

I do that (not at such gruesome levels tho) because I know I gonna rebase my commits, and the changes are so minuscule that they don't deserve a comment.
Something like
-m "optimized"
-m "s" #for "same"
-m "s"
Then just one commit named "optimizations"

@cfood this

@p3rand0r still optimizations is saying the same as just commenting 1.