6 ms·
I often review commit logs of my teams, especially while we are tracking down problems or I'm making sure the release notes capture everything. There has to be
by Ensorceled 7y ago
I often review commit logs of my teams, especially while we are tracking down problems or I'm making sure the release notes capture everything.
There has to be a balance between this and "WIP"; I'm imagining trying to page through the commit log to see what changed when every 1 line change has a 35 line commit associated with it.
- pricechild 7y agoWould `git log --oneline` not help?
- 1f60c 7y agoThat’s the beauty of it, the first 50 characters of the first line (IIRC) will be shown as a summary, and this one summarizes 35 lines in seven words.
- UK-Al05 7y agoI believe there's a standard format for this. The first line is the title, then there's a description. These heavy descriptions of commits, are used quite heavily in linux kernel dev