Learn what Git is the time machine for your files.
A 10-minute lesson: the commit as a sealed photo, the add + commit ritual, branches for experimenting, and the difference between Git and GitHub.
What Git really is, how it seals photos of your project, and why you never lose work again.
The case
Git doesn't prevent disaster: it prevents it from being final. Every commit is a sealed photo you can return to.
In 10 minutes you'll master the ritual: what a commit is, how the photo chain grows, and why branches let you experiment without fear.
What you will learn
- Explain what Git is without confusing it with GitHub
- Seal photos of your project with messages that save you
- Use branches to experiment without breaking main
The Chronicler's log
Edit → seal (commit) → branch to experiment → merge when it shines. With that, “I deleted everything” stops existing.
Repository
The folder that remembers everything.
Commit
The sealed photo with a message.
Branch
The experiment that breaks nothing.
GitHub
The remote: for sharing, not just backing up.
Frequently asked questions
Are Git and GitHub the same?
No: Git is the time machine living on your disk; GitHub is a remote for sharing that history and collaborating.
Do I need to code to use Git?
No: it works for any folder with a history — a thesis, a design folder, or your config files.
Test yourself: Lightning test: photo or save?
What exactly is a commit?
Correct answer: A snapshot of the project, sealed with a message explaining it.
The commit freezes an exact state and welds it to the chain. It's neither automatic nor cloud: you decide when and what gets photographed.
A colleague says: “Git and GitHub are the same”. What do you correct?
Correct answer: Git is the time machine on your disk; GitHub is a remote where you share the history.
Without push, the cloud knows nothing about your repo. Git works alone and locally; GitHub adds collaboration on top.
You want to try a redesign that could break everything. What do you do?
Correct answer: A branch: a cheap experiment that never touches the main line.
Branches exist exactly for that: if it shines, you merge; if not, you toss it and main never even noticed.
The pocket rule — Git is the local time machine; GitHub, the remote for sharing. Commit = a sealed photo with a message, not a “save”.
What you take away
Explain what Git is, read its version history, and save your first file with commits.