✳flâneur — a map of the web's best reading
How to Write a Git Commit Message
cbea.ms · 2,776 words · saved by 2 readers
Commit messages matter. Here's how to write them well.
Contents: Introduction | The Seven Rules | Tips Introduction: Why good commit messages matter If you browse the log of any random Git repository, you will probably find its commit messages are more or less a mess. For example, take a look at these gems from my early days committing to Spring: $ git log --oneline -5 --author cbeams --before "Fri Mar 26 2009" e5f4b49 Re-adding ConfigurationPostProcessorTests after its brief removal in r814. @Ignore-ing the testCglibClassesAreLoadedJustInTimeForEnhancement() method as it turns out this was one of the culprits in the recent build breakage. The cla
Explore this link on the map →saved by
related reading
- How to Write Better Git Commit Messages – A Step-By-Step Guidefreecodecamp.org
- Writing commit messageschiark.greenend.org.uk
- Conventional Commitsconventionalcommits.org
- Short: WiP · Rafał Pastuszaksonnet.io
- Git - user-manual Documentationgit-scm.com
- meks.questmeks.quest
- Command Line Interface Guidelinesclig.dev
- The Git Commands I Run Before Reading Any Codepiechowski.io
- OMBD#21: Master Git Diff With These Not-So-Known Commands | by Jon Portella | ITNEXTjportella93.medium.com
- Git was built in 5 daysgraphite.dev
- Oh Shit, Git!?!ohshitgit.com
- A Bunch of Programming Advice I'd Give To Myself 15 Years Ago | Marcus' Blogmbuffett.com