Working dir
The file on your disk — what your editor shows. Edits land here first.
Every visualization is driven by a Git simulator whose output is verified against real Git. Here is what each part of the stage means — and a live one to try it on.
git commitPress ▶ and watch a file travel from your disk to Staging to a commit. To type your own commands, open the Playground.
The table on the left follows every file through the three places Git keeps it. A version label (v1, v2…) changes when the content changes, and a cell flashes when a command touches it.
The file on your disk — what your editor shows. Edits land here first.
The draft of your next commit. git add copies a version here.
The version in the last commit of the branch you are on.
Under each file name: unchanged, modified, staged, untracked, conflict… exactly what git status would say.
The right side draws your repository. Everything on it comes from the real state after each command — nothing is placed by hand.
One commit, with its short hash and message. Hashes are real: they are computed from the content.
Points from a parent to its child. A merge commit has two parents, so two lines meet.
A branch is just a movable label on a commit (main, feature/login…).
Where you are. It sits next to the branch you are on, or on a commit directly when HEAD is detached.
origin/main and friends: your last known copy of the server’s branches, updated by fetch, pull and push.
An unreachable commit — no branch points at it any more, but it still exists (the reflog can bring it back).
Shown when a lesson uses a remote: the server’s repository above yours, so push and fetch visibly move commits between them.
Every lesson is a list of Git commands. A Git simulator built into the site runs them in your browser — before each release, its output is verified line by line against real Git 2.48.
Interactive commands (add -p, rebase -i) pause on each question so you can read it before the answer is typed.
When Git opens an editor (commit message, rebase todo list, tag message) the stage shows the file being edited.
cat index.htmlcode index.htmlgit add index.htmlLessons are watch-only. To type your own commands, open the Playground (link under every visualization): the graph reacts exactly like in the lessons, and hints suggest the most likely next commands when you get stuck.
A narration line like “a teammate pushes…” means someone else changed the server — the reason a later push or pull behaves the way it does.
A step is split into beats. Each beat changes one thing and explains it in a caption at the bottom of the stage; everything else dims.
The command is typed before anything moves, and the panels change only when its effect lands.
2b4c917 is born — a snapshot of everything in Staging. main moves onto it (HEAD comes along — it points to main)What just happened and why, in one sentence. The panel next to the terminal repeats it with the step’s explanation.
git log --onelineecho "cart.push(item)" >> app.jsecho "export function login() {}" > login.jsgit statusgit add app.js login.jsThe numbered list under the explanation. Click any step to jump to it.
Play it like a video or step through it.
Restart, previous step, play / pause, next step.
Drag to scrub to any moment of the lesson.
0.5× to 2×.
Click the stage, then Space = play / pause, ← / → = previous / next step.
Where the visualizations live.
--force-with-leaseGit ≥ 1.8.5RecommendedThe main visualization covers the everyday use of the command. Each option has its own short visualization — open it from the Options list.
Every option carries a badge: Recommended, When needed or Not recommended, with a one-line reason.
Open the diff in your editor before staging. You can manually edit which changes to include.
$ git add -e app.jsgit add -e opens the whole diff as a patch in your editor; you delete the lines you do not want staged and git applies what is left. It is a hand-edited file, not a repository state change the stage can animate — git add -p is the visual equivalent.
A few options depend on things outside the repository (your editor, file permissions, line endings). They get an explanation card instead of an animation.
$ git switch -c feature/login$ echo "export function login() {}" > login.js && git add login.js && git commit -m "Add login page"$ echo "login()" >> app.js && git commit -am "Call login on load"Real-world walkthroughs played as one continuous story, split into titled sections you can click.
The gear button in the header holds the settings: language, light or dark site, the visualization theme, a colour-blind mode and the text size.
Follow a whole workflow, or pick a command.