Telling stories through your commits
summary
Argues that version history can be the primary documentation and gives three concrete practices: make atomic commits so a WordPress 4.0.1 update isn’t a single 175,000 lines blob, write a one-line title plus why and links (example: Outlook CSS quirk linked to a tracking ticket), and git rebase -i to squash or split development commits before sharing so branches tell the actual intent and fixes that were applied.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:55Naming
- 1:13Automated tests
- 1:56Version control system
- 2:13Your commit history is...
- 2:31Searchable
- 3:33Bug fixes and WordPress 4.0.1 update
- 4:30Minimum viable commit
- 6:45$ git rebase --interactive
related talks
49mWrite history, keep a diary
29mDocumentation Tradeoffs and Why Good Commits Matter
38mGit Best-Practice - Keeping a Diary
46mWrite history, keep a diary
30m7 Tips to Pimp Your Git History
26mA Branch in Time (a story about revision histories)
36mCommit Messages to the rescue!
34mDocumenting the (Ancient) History of Your Project