Each session has one concrete outcome and a short sequence: a section to read, a prediction to make, something to do in the browser simulator or a real repository, and a knowledge check. Durations are estimates of engaged work, not timers. Progress is saved in this browser and shown in My Academy; nothing needs an account.
About 10 minutes
- Understand what enters your next commit
Predict exactly what `git commit` will record, by reading `git status` as three places rather than one.
- Choose a safe way to undo a change
Pick between `restore`, `reset` and `revert` from where the change is and whether anyone else has it — and preview what each would discard.
About 20 minutes
- Recover a deleted branch
Restore a force-deleted branch to its exact last commit using the reflog, and explain why that works and when it stops working.
- Resolve and verify a merge conflict
Read both sides of a conflict, choose a resolution on its merits, complete the merge, and verify the result — or abort cleanly.
About 30 minutes
- Review a branch after rebasing
Clean up a branch with interactive rebase, keep a reference to its old state, and use `git range-diff` to prove the rewrite changed history but not code.
- Diagnose a pull request blocked by required checks
Work a "waiting for status to be reported" pull request through a decision tree — missing check versus failed check, trigger versus filter versus name — and fix the configuration without weakening protection.
Every step links to the full lesson or lab it draws on — the sessions are routes through the curriculum, not a replacement for it.