One real day of git. Done like a human.
A work/play walkthrough of a realistic session — small atomic commits, conventional prefixes, and a clean story. No 50-file blobs, no lazy "update" messages.
Why atomic matters
An atomic commit is one logical change — easy to review, easy to revert, easy to cherry-pick. A 50-file mega-commit is a black box nobody dares to touch.
The 50 / 72 rule
Subject under 50 characters, detail wrapped at 72. If a change needs more than one paragraph, it deserves its own commit.
The day at a glance
Act 1
The first commit
Scaffold the repo the same way a cautious human does — one clean chore commit.
5 commands
Act 2
Three changes, three commits
Split a messy work session into small, reviewable, atomic commits.
6 commands
Act 3
Ship it calmly
Put the experiment on a branch, then land it without drama — even when a conflict tries to ambush the merge.
6 commands
Step 1
A blank directory, full of promise
You're starting a tiny website from scratch. The first real git act is to give it a repo — git won't do anything useful until it has one.
git initgit init makes the .git directory — objects, refs and the index live inside it.