Optional Git and Version History
Updated · Tech checked
Snapshots first, Git later: copy the folder today, learn commit history only when curious, never as a gate.
The direct answer
Version history in this course is folder copies first, Git only if curious. Copy quote-app to quote-app-2026-10-04 before risky changes. That habit alone satisfies every lab. Git adds named history on top.
If curious: the five commands
- init once in the project folder.
- add the three files.
- commit with a plain message, e.g. working quote math.
- log to see the history.
- checkout the earlier commit to undo, keeping a copy of user data first.
Worked example
Lab A17 breaks a change on purpose, then restores the earlier snapshot while keeping the user's saved data. The Git version is the same idea with names and messages.
Errors to avoid
- Learning Git before building. Build first; history is support.
- Committing secrets. The secret rule applies to history too.
- Pushing personal practice to public hosting. Local history is enough here.
Frequently asked questions
Is Git required for the certificate? No. Snapshots plus the structured delivery record are sufficient.
When is Git worth it? When you change files daily and want named undo points with messages.
Sources
- Course lessons M06 and lab A17 (this site).
- Git official docs: git-scm.com/docs (checked 2026-10-04).