Branching, committing, pulling, and merging discipline. The basics that let multiple people, and multiple agents, work in parallel without losing each other's work.
If the project is the building, GitHub is the keys. Lose the keys, lose the building.
More importantly, GitHub is what makes multi-agent and multi-human collaboration possible. Without it, every change overwrites someone else's, every what-changed question takes ten minutes, every rollback is a panic.
You do not need to be a Git wizard. You need five operations, executed cleanly, every time. Beyond these five, you can stay in dangerous-water territory for a long time without ever drowning.
The five operations are easy. The discipline of using them well is what separates a team that ships from a team that constantly recovers.
GitHub is what makes multi-agent and multi-human collaboration possible. Two agents cannot edit the same file at the same time. Branches let them work in parallel without colliding.
When the developer agent and the writer agent both want to edit the homepage, you put each on its own branch. They each commit. You merge in turn. No one overwrites anyone.
Use the Hello World repo from Protocol 02 (or any small repo you own). You will branch, commit, push, merge, then deliberately create a merge conflict to learn how it feels in safety.
git pull. Then git checkout -b experiment/badge. You are now on a parallel line of work.
Add a small badge or note to the homepage. Tell Claude or do it by hand.
git add and git commit -m "add badge". Then git push -u origin experiment/badge.
On GitHub, open a PR from your branch to main. Click Merge. Confirm the change is live on main.
On main, change the headline. On a new branch (experiment/badge-2), change the same line to something else. Push both. Try to merge. GitHub will refuse and show you the conflict.
Open the file in your editor. Choose which version wins, or combine them. Commit the resolution. Merge. The conflict is gone. The next one will not scare you.
The five operations live in your daily flow. The first merge conflict is behind you, in safety. Future merge conflicts feel like a Tuesday, not a crisis.
You run the full daily flow three times, branch, merge, and resolve one deliberately-created conflict so you never panic at one again.