Earlier quoted context omitted.
Tbh I’m (loosely) following commit message best practices in all of my projects out of irrational fear of being viewed as unprofessional. But never needed that effing prose in my workflow. Maybe a keyword from time to time. I’m using code, not messages to navigate history, and in a rare occasion. If all my messages turned into “i” I’d lose nothing, because all rationales and essentials are in code comments. I’d bette…
Commit comments are how you find code diffs. Focus on what/why in your commit messages. If you can’t articulate that in your commit messages, I can almost guarantee you’re thinking deeply enough about your code changes.
I appreciate advices, but I believe this one is not on point I expressed, as it only reiterates on a premise that I follow already but find mostly useless irl.