Basically boils down to having an imperative statement with no period that is less than 50 characters for the subject and then lines of 72 characters or less for the body with subject and body being separated by a blank line.
Of course, ending with an Issue #XXX when relevant to tie the commit to an issue on GitHub.
After doing it that way for a bit, I now mostly follow a similar structure for most commits on all projects.
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.
I have had a few projects where it was required to follow these rules: chris.beams.io/posts/git-commit/
Basically boils down to having an imperative statement with no period that is less than 50 characters for the subject and then lines of 72 characters or less for the body with subject and body being separated by a blank line.
Of course, ending with an
Issue #XXXwhen relevant to tie the commit to an issue on GitHub.After doing it that way for a bit, I now mostly follow a similar structure for most commits on all projects.