There’s a community standard out there called Conventional Commit for structured git-commit messages. If you don’t know about it already, it recommends a strict type(scope?): description format for describing a code change in a repo.
I find a commit message describing consequential effect and intended goal/change more useful than technical details.
100% this! I’m reminded of this post on “why” is better than “what”, as the what is self-explanatory from looking at the changeset, whereas the why requires context that should be captured in the commit message.
100% this! I’m reminded of this post on “why” is better than “what”, as the what is self-explanatory from looking at the changeset, whereas the why requires context that should be captured in the commit message.