Outcome. Predict exactly what `git commit` will record, by reading `git status` as three places rather than one.
Before you start: Git installed and a first commit made
The duration is an estimate of engaged work, not a timer — nothing here waits. Steps marked "Check" and "Practice" are verified in the browser; "Read" and "Lab" steps are yours to confirm.
Read this section and the one after it ("Reading git status"). Look for the two columns in `git status --short` — they are two different places.
- Predict
Predict: what does this commit contain?
≈ 1 min✓ doneAnswer before you look anything up.
Open Practice Mode on the lab page and choose "Unstage a file without losing the edit". Success is checked against the repository state.
Scenario: Unstage a file without losing the edit — completes automatically when the simulator's check passes.
Four questions. A wrong answer shows the reasoning immediately.
Completes when the knowledge check on that page has been attempted.
Session complete
Next: Choose a safe way to undo a change — Now that you can see where a change lives, the next skill is putting it back — with the right tool for each place.
Keep building your Git skills. Get one practical technique, one workflow, and one security lesson each week. Modern Git Weekly is not taking subscriptions yet — read thesample issue, or follow new lessons by RSS.
When you are done: Choose a safe way to undo a change. Now that you can see where a change lives, the next skill is putting it back — with the right tool for each place.
How did this go?
Unexpected output. Compare your output with the expected block line by line; the first differing line is usually the cause. Then check the version-sensitive notes.
Missing prerequisite. Most "stuck" moments here come from one earlier concept. The prerequisites list names it; the learning path puts it in order.
Unclear explanation. Read the explanation section, then the mental model, then retry the step — the command usually makes sense once the model is in place.
Instructions did not match my environment. Check `git --version` and your shell (Git Bash vs PowerShell vs zsh). Platform notes on the page name the differences that matter; the verification step confirms you are back to a known state.
Good. The next step is to do it without the page open — or move to the recommended next activity below.
All help on this page: Git troubleshooting decision tree · Find the lesson that comes before this one · How Git works — the model behind the commands · Recover a lost commit (lab)