Communicating Intent Through Git
summary
Argues that git is a communication tool and shows concrete practices: use a commit template and write an imperative 50‑char summary, put a 72‑char‑wrapped body answering why and linking sources, stop git commit -m, use git add -p to stage hunks, use git blame (alias git thank) to surface rationale, rebase to reword bad messages, attach LICEcap GIFs to PRs, follow Vincent Driessen branching, and keep PRs small — an anecdote warns a single 43‑file PR becomes unreviewable.
AI-written summary · about
chapters (29)
- 0:00Intro
- 3:30Git Communication Tool
- 9:32Summary
- 13:20Blame
- 13:47Get thanked
- 14:02Why
- 15:07Shell Words
- 16:12Email Example
- 17:11Search
- 17:26Favicons
- 17:55Create a gem
- 18:05Start with a baseline
- 18:27Build an abstraction
- 18:53Add details
- 19:28Change parameters
- 20:02Add patches
- 21:02Add tests
- 21:40Staged tests
- 22:15Commit messages
- 23:58Break one of the rules
- 24:30Final commit
- 25:09Rebasing
- 25:38Commit
- 26:32Branch Model
- 28:47Pull Requests
- 29:59Licecap
- 30:57Code Reviews
- 35:20Takeaway
- 36:07Taking a proactive approach
