Git Best-Practice - Keeping a Diary
summary
Explains concrete habits and commands that make history useful: keep atomic commits, split formatting from logic, use git add -p, amend or git rebase -i to rewrite local history, and run git bisect, grep and -S searches to find when and why lines changed. Cites a 2016 snapshot of ~151 million non-merge commits full of “initial commit” and “update README” as evidence. Recommends one-line subjects (~50 chars) and 72-char body wrapping, branch-by-feature with rebasing to avoid merge bubbles, and hooks to enforce metadata.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:18What is a diary
- 2:05How to keep a diary
- 6:33Git Basics
- 12:18Good History
- 17:53Purity
- 25:42Graphs
- 29:24Commit Messages
