Commit 1cdcab0
committed
doc: slightly relax 50 character rule
Allow commit message first line to exceed 50 chars if necessary
PR-URL: #16523
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Evan Lucas <evanlucas@me.com>
Reviewed-By: Anatoli Papirovski <apapirovski@mac.com>
Reviewed-By: Refael Ackermann <refack@gmail.com>
Reviewed-By: Gibson Fahnestock <gibfahn@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>1 parent 980ebd2 commit 1cdcab0
1 file changed
Lines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -309,8 +309,8 @@ notes about [commit squashing](#commit-squashing)). | |||
| 309 | 309 | A good commit message should describe what changed and why. | |
| 310 | 310 | ||
| 311 | 311 | 1. The first line should: | |
| 312 | - - contain a short description of the change | ||
| 313 | - - be 50 characters or less | ||
| 312 | + - contain a short description of the change (preferably 50 characters or less, | ||
| 313 | + and no more than 72 characters) | ||
| 314 | 314 | - be entirely in lowercase with the exception of proper nouns, acronyms, and | |
| 315 | 315 | the words that refer to code, like function/variable names | |
| 316 | 316 | - be prefixed with the name of the changed subsystem and start with an | |
0 commit comments