Transparency Report

Visualization Accuracy

Nothing on the stage is drawn by hand. Each visualization is a list of Git commands that a Git simulator built into the site runs in your browser. The terminal output is generated by it, and every animation is derived from what actually changed in the repository. To keep the simulator honest, before each release every step is replayed in real Git 2.48 and the two outputs are compared line by line.

333 visualizations
2134 / 2134 steps match real Git
15 options explained instead of animated
Last check: Sep 29, 2026

Git Commands

CommandOutput vs real GitStatus
git add
67 steps
Verified
git commit
133 steps
Verified
git reset
29 steps
Verified
git branch
69 steps
Verified
git checkout
58 steps
Verified
git merge
39 steps
Verified
git rebase
48 steps
Verified
git cherry-pick
48 steps
Verified
git stash
50 steps
Verified
git fetch
26 steps
Verified
git pull
80 steps
Verified
git push
89 steps
Verified
git log
24 steps
Verified
git status
23 steps
Verified
git diff
22 steps
Verified
git restore
18 steps
Verified
git rm
11 steps
Verified
git mv
3 steps
Verified
git clean
22 steps
Verified
git switch
24 steps
Verified
git tag
18 steps
Verified
git revert
16 steps
Verified
git show
10 steps
Verified
git reflog
8 steps
Verified
git init
9 steps
Verified
git clone
14 steps
Verified
git config
13 steps
Verified
git remote
8 steps
Verified
git blame
12 steps
Verified
git annotate
3 steps
Verified
git grep
20 steps
Verified
git describe
15 steps
Verified
git shortlog
13 steps
Verified
git show-branch
4 steps
Verified
git whatchanged
3 steps
Verified
git version
3 steps
Verified
git help
6 steps
Verified
git notes
18 steps
Verified
git bisect
25 steps
Verified
git worktree
12 steps
Verified
git sparse-checkout
17 steps
Verified
git archive
13 steps
Verified
git bundle
10 steps
Verified
git format-patch
10 steps
Verified
git am
5 steps
Verified
git range-diff
4 steps
Verified
git merge-tree
4 steps
Verified
git rerere
9 steps
Verified
git fsck
10 steps
Verified
git fast-export
7 steps
Verified

Explained, not animated (22)

The simulator cannot show these honestly (graphical tools, external programs, storage internals, signatures, commands newer than Git 2.48), so their page explains them instead. There is no animation to compare with real Git.

Real-World Scenarios

ScenarioOutput vs real GitStatus
Your First Git Commit
10 steps
Verified
Cloning a Repository
8 steps
Verified
Undo the Last Commit
13 steps
Verified
Feature Branch Workflow
14 steps
Verified
Resolving a Merge Conflict
10 steps
Verified
Hotfix a Production Release
12 steps
Verified
Rebase a PR onto the Latest Main
11 steps
Verified
Clean History Before Merging
10 steps
Verified
Recover Lost Work
10 steps
Verified
Roll Back a Bad Merge
9 steps
Verified
Urgent Fix Mid-Feature
12 steps
Verified
Tag and Ship Versions
9 steps
Verified
Split a Commit for Review
8 steps
Verified
Clean Up Merged Branches
11 steps
Verified
Shallow Clones in CI
6 steps
Verified

How is this verified?

Terminal output

A test replays every lesson in a real Git 2.48 repository with the same files and dates, then compares each command’s output, exit status and editor contents with what the site shows. Only machine-specific details are normalised (hashes, paths, transfer speed).

Animations

Nodes, branch labels, HEAD, the three file areas and the remote are drawn from the repository state after each command — so the picture can only show what the simulator actually did (and that is verified against real Git). Every lesson also asserts its key facts (branch, clean tree, conflicts, commit subject) at build time.

Checked on every build

A lesson that breaks any of these rules stops the build:

  • ✓ Every command runs; steps meant to fail really fail
  • ✓ The lesson’s expectations hold (branch, clean tree, conflicts, HEAD commit)
  • ✓ No hand-written output, hashes or positions
  • ✓ Every step shows something (output or a visible change)
  • ✓ Option lessons really use their option
  • ✓ Recommendation badges match the option documentation
  • ✓ Same starting repository on every page
  • ✓ One idea per step, explained in a full sentence

Limits: a few options depend on things outside the repository (your editor, file permissions, nested repositories, line-ending settings, sparse checkout). Those are explained with a “How it works” card instead of an animation. Spotted something that differs from your Git? Report it.