Then reuse it by running git commit -F .git/COMMIT_EDITMSG .
A widely adopted industry standard is the 50/72 Rule , which dictates that a commit title should be 50 characters or less, and body paragraphs should wrap at 72 characters.
Its primary purpose is to act as a for the message editor you have configured (like Vim, Nano, or VS Code). COMMIT-EDITMSG
: Begin your subject line with a command verb (e.g., "Fix layout bug" instead of "Fixed layout bug" or "Fixes layout bug").
# <type>(<scope>): <subject> (Max 50 chars) # |<----------------------- 50 ------------------------>| # # <body> (Wrap at 72 chars) # |<------------------------------------------------------------------------- 72 ->| # # <footer> # Closes # # # --- # Types: # feat, fix, docs, style, refactor, test, chore, perf, ci, build # Then reuse it by running git commit -F
The existence of COMMIT_EDITMSG is a technical detail, but its purpose is purely practical: to facilitate the writing of a . A great commit message is arguably as important as the code change itself. It serves as documentation for your future self and for other developers.
: Git pauses the terminal session and opens your configured default text editor, passing it the path to .git/COMMIT_EDITMSG . : Begin your subject line with a command verb (e
To understand this file, it helps to look at the lifecycle of a standard commit command: