Gitastic

Stop memorising git.
Start seeing it.

Git feels like magic spells until you can see what each command does to your history. Gitastic animates every command on a live commit graph, then lets you try it yourself in a safe, simulated terminal.

Start lesson 1 →Open the sandbox
$ git commit -m "Initial commit"
220addd Initial commit220adddInitial commitHEAD = where you are. It points at the current branch.HEAD →Branch "main" — a movable pointer (current branch: moves when you commit)main
Step 1

Learn

A short mental model with an analogy. No command soup.

Step 2

Watch

Step through an animated demo: commands on the right, the graph reacting on the left.

Step 3

Check

Quick questions, some asking you to read a graph and predict what happens.

Step 4

Practice

A mission in a real-feeling terminal. The graph updates as you type.

The learning path

Sixteen lessons covering the ~20% of git you will use 80% of the time — plus the rescue tools for when things go sideways. Around 121 minutes in total.

Part 1

The mental model

Snapshots, the three areas, and reading history. Everything else builds on this.

01Commits are snapshotsThe one idea everything else in git is built on.02The three areasWorking directory → staging area → repository. Where your changes actually live.03Reading historylog, show, diff — and how to point at any commit.
Part 2

Branching

Branches are just sticky notes on commits. Merge, resolve conflicts, rebase.

04Branches are just pointersA branch is a sticky note on a commit. That is all it is.05MergingBringing work back together: fast-forward or merge commit.06Merge conflicts, calmlyGit asks you a question. You answer it. That is all a conflict is.07Rebase: replaying commitsMove your work onto a new starting point for a straight-line history.
Part 3

Working with others

Remotes, fetch vs pull, push, and the pull-request workflow.

08Remotes & cloneYour repo, their repo, and the sticky notes that remember where they were.09Pull & pushSharing work in both directions — and what "rejected" really means.10The feature-branch & pull-request workflowHow most teams actually ship changes, step by step.
Part 4

Undo & rescue

restore, reset, revert, stash, and the reflog safety net.

11The undo toolboxrestore, reset, revert, amend — which one, and when.12Stash: the pocketPark half-done work, switch context, pick it back up.13Detached HEAD & the reflog safety netCommits are very hard to truly lose, and here is why.
Part 5

Power tools

Cherry-pick, worktrees, tags and tidy history.

14Cherry-pick: copy one commitTake exactly the commit you need — and nothing else.15Worktrees: many desks, one repoWork on two branches at the same time — without stashing or switching.16Tags & tidy historyMark releases forever, and clean up your commits before you share them.