Status → branch → diff → commit
Short, narrated lessons. Understand an idea, see an example, then try it yourself.
Illustrated lesson with synthetic narration. Example boards explain the workflow; they are not recordings of Codex running.
Transcript & lesson chapters
0:00 · Understand the idea
Status → branch → diff → commit. A branch isolates a line of work. Inspect status before changing branches, review the diff, stage only intended files, and commit a coherent change.
0:15 · See a concrete example
See a concrete example. In a disposable Git repository, run git status, create a branch with git switch -c practice-heading, edit one heading, and run git diff. Review before staging that file and committing.
0:31 · Try it yourself
Pause the video and complete the exercise.
0:40 · Avoid this mistake
Avoid this mistake. Staging everything without checking for secrets or other people’s changes. Stage named files only.
0:51 · Check your result
Check your result. git show --stat displays only the intended files; git status makes remaining uncommitted work visible. Open the lesson below, try the exercise, and mark it complete only after checking the result.
Lesson notes
A branch isolates a line of work. Inspect status before changing branches, review the diff, stage only intended files, and commit a coherent change.
Try it yourself
In a disposable Git repository, run git status, create a branch with git switch -c practice-heading, edit one heading, and run git diff. Review before staging that file and committing.
Verify your result
git show --stat displays only the intended files; git status makes remaining uncommitted work visible.
Official references
Git · diff ↗Git · switch ↗Git · revert ↗Product interfaces and access can change. Use the linked official guide for current installation and account requirements.