Hallo! Yes Twitter is a horrendous place for pretty much anything I find...
So I don't have an answer and I don't expect every use-case is the same as my use case but what I do think that I am up to is probably not a huge outlier to what others may do.
Agree there's "lots of dev" that probably shouldn't be commited and then things probably don't change very much until the next bout of "changing things around"
I have this problem in general with git and spurious commits I make as I go along irritate me. For my sins I often reset HEAD~X on my working feature branch
I feel I want auto-commit as I don't want to take the chance an important change gets lost. I want to "know" that changes we made got committed / backed up and not have to think about it
This of course leads to the commit message business. I have used the git hooks that force you to enter a commit message and actually I think I can live with them. For me I think a checkbox to make it a requirement to enter a message in a pop up box on every commit would be a good thing for me...
Just my 5c!
[Edit: OR - a thought occurs - NodeRed could auto generate some information about what nodes changed and so forth for the default message which could then be changed by the committer - cor that would be CLEVER! ]