--- title: Writing Good Git Commit Messages --- 1. Separate subject from body with a blank line 2. Limit the subject line to 50 characters 3. Capitalize the subject line 4. Do not end the subject line with a period 5. Use the imperative mood in the subject line 6. Wrap the body at 72 characters 7. Use the body to explain what and why vs. how **A properly formed git commit subject line should always be able to complete the following sentence:** > If applied, this commit will _`<>`_ **For example:** * If applied, this commit will **_Refactor subsystem X for readability_** * If applied, this commit will **_Update getting started documentation_** * If applied, this commit will **_Remove deprecated methods_** * If applied, this commit will **_Release version 1.0.0_** * If applied, this commit will **_Merge pull request #123 from user/branch_** **Notice how this doesn't work for the other non-imperative forms:** * If applied, this commit will _fixed bug with Y_ * If applied, this commit will _changing behavior of X_ * If applied, this commit will _more fixes for broken stuff_ * If applied, this commit will _sweet new API methods_ **Remember:** _Use of the imperative is important only in the subject line. You can relax this restriction when you're writing the body._ **Reference:** http://chris.beams.io/posts/git-commit