By setting git config commit.template , you can pre-fill COMMIT_EDITMSG with a checklist or a specific format your team follows.
Using git commit -m "message" bypasses the creation of this file entirely, which is efficient for small fixes but discouraged for complex features that require detailed documentation [5.6]. Customizing the Experience
When you execute git commit , Git performs several background tasks: It creates the COMMIT_EDITMSG file.
Using COMMIT_EDITMSG makes this formatting much easier to manage than typing long strings into a terminal prompt [5.3, 5.4]. Troubleshooting and Common Scenarios
A concise summary (max 50 characters) followed by a blank line.
For many beginners, the first encounter with COMMIT_EDITMSG is an accidental trip into Vim. To save your message and exit, type :wq . To abort, type :q! .
You can actually influence what appears in COMMIT_EDITMSG before you even start typing.
The existence of this file encourages developers to move away from "one-liner" commits and toward the industry-standard . According to many commit message guides , a well-structured message should have:
A detailed explanation of the why behind the change, wrapped at 72 characters.
Once you save and close the file, Git reads the content, strips out the comments, and uses the remaining text as the permanent message for that commit. The Role of COMMIT_EDITMSG in Best Practices