Git: a history of changes
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
Git: a history of changes. Git tracks versions of project files. A commit is a named snapshot of staged changes. Git is not an automatic backup of every file on your computer.
0:15 · See a concrete example
See a concrete example. Imagine notes.txt changes from “Hello” to “Hello, team”. Write a one-line commit message describing that change. The Git chapter later shows the commands.
0:30 · Try it yourself
Pause the video and complete the exercise.
0:39 · Avoid this mistake
Avoid this mistake. Assuming untracked files are protected. Check Git status and keep a separate backup where needed.
0:49 · Check your result
Check your result. Your description explains what changed, rather than only saying “update”. Open the lesson below, try the exercise, and mark it complete only after checking the result.
Lesson notes
Git tracks versions of project files. A commit is a named snapshot of staged changes. Git is not an automatic backup of every file on your computer.
Try it yourself
Imagine notes.txt changes from “Hello” to “Hello, team”. Write a one-line commit message describing that change. The Git chapter later shows the commands.
Verify your result
Your description explains what changed, rather than only saying “update”.
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.