Saving Your Work: Git & Version Control
Welcome aboard
Ahoy — Pip here, your lighthouse keeper. Have you ever saved a file as final, then final-v2, then final-REAL-this-time? That little mess is the exact problem version control solves, and it solves it beautifully.
The trick: think of your work as writing a book. Every so often you save a clean snapshot — a save-point you can always return to. You can keep a private draft of a wild new chapter without touching the real manuscript. And if a change turns out badly, you can walk back to any earlier snapshot, calm and unhurried.
That's the whole idea. In this course we'll meet the tool called Git one plain piece at a time — no memorizing, just understanding. By the end you'll keep a real history of your own work. Let's cast off. 🔦
- Why Version Control Exists Free previewVersion control is a careful record of every version of your work, so you never lose a good draft or fear a bad change. Here's the problem it solves.
- Meet Git and the Repository 🔒Git is the program that does version control, and a repository is the folder it watches and remembers. Here's how they fit together, told as a bound notebook.
- Commits, the Save-Points 🔒A commit is a permanent, labeled snapshot of your whole project at one moment — the single most important idea in version control. Here's how it works.
- Staging — Choosing What to Save 🔒Before a commit, Git lets you pick exactly which changes go in using a holding area called the staging area. Here's why that extra step is a gift.
- Reading Your History 🔒Your commits form a timeline you can scroll through, and each one shows exactly what changed. Here's how to read the story your save-points tell.
- Undoing Changes Safely 🔒Version control lets you walk back a bad change without losing the good ones — the safety net that makes you brave. Here's how undo actually works.
- Branches — Parallel Drafts 🔒A branch is a private copy of your project where you can try anything without touching the real version, then bring it back if it works. Here's the freedom that unlocks.
- Merging & Putting It Together 🔒Merging folds a finished branch back into the main version, and sharing online backs it all up. Here's how every piece fits into one calm workflow.
What you get
- 📚8 plain-English lessons, taught by Pip — no jargon, no prior tech knowledge needed.
- ✅A quick quiz after every lesson, so what you learn actually sticks — and your progress saves as you go.
- 🎓A verifiable Portmint Certificate when you finish — reviewed by a real person, and worth listing on your résumé and LinkedIn.
- ♾️Lifetime access, yours for good — learn at your own pace, revisit anytime.
- 🐙Ask Pip anything as you learn — he's right here on the page.
- 💚Free for Portmint employees — just sign in with your Portmint account.
Start free — unlock the rest when you're ready
The first 1 lesson is a free preview. Then $129 unlocks all 8 lessons plus the certificate — yours for good, no subscription.
Start the free preview →🎓 Capstone — build it, share it, get certified
Finished the lessons? Prove it. Build a real version-controlled project of your own — a personal journal or recipe collection with a tidy history of save-points, a side branch you tried out, and at least one confident undo that uses what you learned here, then share it publicly and thank Portmint for the education, and email it to capstone@portmint.net. A real person on the Portmint team reviews every submission — pass, and you earn a verifiable Portmint Certificate worth listing on your résumé and LinkedIn. (Optional, but it's how a course becomes something real.)
Submit my capstone →