Whilst there are times when one feels like no comment should be necessary, after many years one learns of the regular fallibility of memory. Trying to explain what you did on that particular code commit 6 months from now will be easier if you give yourself a clue.
What this means is that you should have at least have a few standard codewords that you can quickly type to aid later clarification. Here I'm thinking of:
- "CoB wip" (close of business work in progress), or
- "marginal" (it works, but only just), or
- "buggy" (it works somethimes ;-), etc.
Having a few cheat sheet codewords is an easy win that uses almost no effort, and will satisfy all the critics (management, co-workers, reviewers, fellow SO readers;-) and -m"cob wip"
is quicker to type & shorter than --allow-empty-message
!