Deterministic main branch + fix two claims (#5,#13,#16) (#56)

Co-authored-by: claude <claude@jpaul.io>
Co-committed-by: claude <claude@jpaul.io>
This commit was merged in pull request #56.
This commit is contained in:
2026-06-22 14:58:51 -04:00
committed by Claude (agent)
parent e2a53c8259
commit 848ad14e3c
7 changed files with 33 additions and 12 deletions
@@ -47,8 +47,9 @@ Strip the mystique and a branch is **a named, movable pointer to a commit.** Tha
definition. Your commit history is a chain of snapshots (Module 2); a branch is a sticky label that
points at one of them and *moves forward* every time you commit on it.
When you ran `git init` in Module 2, Git made one branch for you automatically — usually called
`main`. Every commit you made moved the `main` label forward. You were "on a branch" the entire time
When you ran `git init -b main` in Module 2, Git made one branch for you automatically — named
`main` (the `-b main` is what guaranteed that name; in this course your repo is always on `main`).
Every commit you made moved the `main` label forward. You were "on a branch" the entire time
without thinking about it.
The thing that surprises people coming from an ops background: **creating a branch copies nothing.**