We do one person per branch with rare exception. When trying to piece together past changes while debugging I basically don’t care what the commit messages are,

We do one person per branch with rare exception. When trying to piece together past changes while debugging I basically don’t care what the commit messages are, I use JetBrains’ “show history for selection” in most cases. Much more useful to me than the messages is the changeset file name highlighting so I can see which files I’ve touched for the thing I’m trying to accomplish right this second. Pushing resets that. So the push is based on “I’m thinking about a new thing now”. Often my commit messages are “x” because there is no cohesion to anything since my last push, I went around making a bunch of nit picks while exploring some code path(s). If it works for me and my team, it’s the right way. Same for everyone else.