3 ms·
If you make lots of small commits, a single line is enough.
by twic 6y ago
If you make lots of small commits, a single line is enough.
- g-b-r 6y agoI do make lots of awfully small commits, and a single line is rarely enough (but sometimes it indeed is)
- MaxBarraclough 6y agoI generally disagree. Someone already linked to [0]. The background there is quite involved, and it doesn't go away if you break down the commit into many smaller ones. You could argue that sort of write-up belongs on a task-tracker like Jira rather than in a git commit message, but that's a different question. Besides, overly small, overly numerous git commit messages are clunky. They clutter the commit graph without adding value, making it harder to get a clear picture of the work history in the repo. There's a happy middle-ground for the size of a commit: it should correspond to a meaningful unit of work, not the smallest committable unit of work. Of course, using too few very large commits is a problem too. Perhaps, as gspr says, a single-line format may make sense in some instances. If a formalised format is used (as shown in [0]) then of course you'll never have the option. [0] https://github.com/golang/go/commit/5779bb4e92911271583faa1365fd12be2c3894ee https://github.com/golang/go/commit/5779bb4e92911271583faa13...