Recap and Practice

Key takeaways

• Git is save points for your project — a full timeline you can jump back to, which is what lets you turn the AI loose without fear.
• The core rhythm is add → commit → push: stage your changes, save them as a commit with a clear message, and send them up to GitHub for backup and sharing.
• Branch before anything big, and read the diff before every commit — that's how you catch the AI deleting something it shouldn't.
• A .gitignore keeps secrets (like .env) and junk (like node_modules/) out of your history. A secret committed to GitHub is leaked forever, even if you delete it later.
• You can let the AI run the commands, but you stay responsible for understanding what each one did — especially destructive ones like reset --hard.

Try it

Make a brand-new folder and run the whole loop yourself, by hand: git init, create a .gitignore with .env in it, add a simple notes.txt file, then git add . and git commit -m "Initial commit". Now run git log --oneline to see your save point, edit the file, and run git diff to watch Git show you exactly what changed. You've just used every core habit in this chapter on a project where nothing can go wrong.

Prompt of the chapter

I'm learning Git as a beginner and I want you to run the commands for me,
but teach as you go. For the task below:
<describe what you want to do — e.g. "save my current work" or "try a risky change safely">

- Tell me which Git commands you'll run and what each one does in plain English.
- If anything is destructive (reset --hard, force-push, deleting a branch),
  warn me clearly and explain what I'd lose before doing it.
- Before any commit, show me the diff and summarize what changed.
- Remind me if there's anything in the change that shouldn't be public (secrets, keys).