Some of the examples remind me of guidance for commenting in code i.e. focus more on 'why', less on 'what' or 'how'.
Commit messages should have related/closed issues/bugs, but they could also have the 'why' messages you mention. I am wary of introducing more places to forget to check.
Maybe some sort of markdown in the commit logs to distinguish procedural issue tracking from useful commentary?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Some of the examples remind me of guidance for commenting in code i.e. focus more on 'why', less on 'what' or 'how'.
Commit messages should have related/closed issues/bugs, but they could also have the 'why' messages you mention. I am wary of introducing more places to forget to check.
Maybe some sort of markdown in the commit logs to distinguish procedural issue tracking from useful commentary?