Tavern & Tools · Quest 3 · Save points with Git

Quest 3 · Save points with Git

Quest 3 · hands-on · ~30 min

30:00

🎯 Mission

You start with: the quest-log folder from Quest 2, and Git installed (git --version prints a version).

You finish with: a Git repo with two commits you can see in the history.

Quest complete when: git log --oneline shows two commits.

+60 XP🏆 Save Point Unlocked

Step 1 · Tell Git who you are (once per computer)

git config --global user.name "Your Name"
git config --global user.email "you@example.com"

Step 2 · Start tracking the folder

📝 Working dirfiles you edit📋 Staginggit add💾 Commitgit commit☁️ GitHubgit push
Git's three boxes, plus GitHub. Changes move left to right, one deliberate step at a time.
cd quest-log
git init
git status

✅ You should see: "Untracked files: README.md" in red. Git sees the file but isn't saving it yet.

Step 3 · Stage, then commit

git add README.md
git status
git commit -m "Start my quest log"

✅ You should see: README.md turns green after git add (staged), then commit prints "1 file changed".

Step 4 · Change something and commit again

echo "- Day 1: learned the terminal" >> README.md
git diff
git add README.md
git commit -m "Log day 1"
git log --oneline

✅ You should see: git diff shows your new line with a +, and the log lists two commits, newest first.

A commit is a save point. git add picks what goes in the save; git commit writes it. Mess up later? Load an old save.

💡 What just happened (plain English)

Git is how every team shares code and how you undo mistakes. The habit to build now: small change → add → commit with a message that says why.

🏁 Checkpoint

  • ☐ git status shows a clean tree
  • ☐ git log --oneline lists two commits
  • ☐ I can explain the difference between add and commit

🏆 Tick every box → achievement unlocked: Save Point Unlocked (+60 XP)