tbaggery - A Note About Git Commit Messages
I want to take a moment to elaborate on what makes a well formed commit message. I think the best practices for commit message formatting is one of the little details that makes Git great. Understandably, some of the first commits to rails.git have messages of the really-long-line variety, and I want to expand on why this is a poor practice.
19 Apr 2008 I want to take a moment to elaborate on what makes a well formed commit message. I think the best practices for commit message formatting is one of the little details that makes Git great. Understandably, some of the first commits to rails.git have messages of the really-long-line variety, and I want to expand on why this is a poor practice. Here’s a model Git commit message: Capitalized, short (50 chars or less) summary More detailed explanatory text, if necessary. Wrap it to about 72 characters or so. In some contexts, the first line is treated as the subject of an email…
saved by
related reading
- How to Write a Git Commit Messagecbea.ms
- How to Write Better Git Commit Messages – A Step-By-Step Guidefreecodecamp.org
- Writing commit messageschiark.greenend.org.uk
- Conventional Commitsconventionalcommits.org
- Semantic Commit Messages · GitHubgist.github.com
- Git at any scalecursor.com
- The comprehensive guide to writing the best PR title of all timegraphite.dev
- Short: WiP · Rafał Pastuszaksonnet.io
- Command Line Interface Guidelinesclig.dev
- How Core Git Developers Configure Git | Butler's Logblog.gitbutler.com
- Git from the Bottom Upjwiegley.github.io
- meks.questmeks.quest