Git for non-technical people: version control without fear

You’ve probably lost work before. You edited a document, saved over the original, realized your edit was wrong, and couldn’t get it back.

Git prevents this. Every time you save (Git calls it “commit”), Git saves a complete snapshot of your work. You can always go back. You can see what changed. You can experiment without fear.

For small businesses and solo workers, Git is one of the most useful tools you can learn.

Core concepts (the mental model)

Repository (Repo): Your project folder. All your files, tracked by Git. Think of it as “this is my work.”

Commit: A snapshot in time. You decide when to save. “At 3pm on Tuesday, I finished version 1.0. This is what it looked like.” Git stamps it with the date, who made the change, and a message explaining why.

History: Git keeps a complete record of every commit. You can see: “Week 1: added blog post. Week 2: fixed layout. Week 3: fixed typo.” And go back to any point.

Push: Send your commits to the cloud (like GitHub). Now your work is backed up and accessible from anywhere.

Pull: Download the latest version from the cloud, so you have everyone’s work.

Branch: A parallel timeline. You can experiment on a branch without affecting the main version. When you’re happy, you merge it back.

Why Git matters for AI agents

When an AI agent works for you, you want to know: what did it change? If something broke, can I undo it instantly?

Git answers both:

Tracking changes: After an agent finishes a task, you can see exactly what it modified. “Ah, it changed these three lines. That’s why the page looks wrong.”

Instant recovery: If an agent makes a mistake, you roll back to the previous commit. One command. Done. No panic.

Experimentation: You can tell an agent, “Try this risky approach on a new branch. If it works, merge it. If not, delete the branch.” Zero risk.

This is why every AI agent should work inside a Git repository.

The simplest workflow

1. Create a repo. Folder with Git initialized. git init in the folder.
2. Make changes. Edit files normally.
3. Commit when stable. When something works, run git commit -m "Fixed login bug". You’ve saved a snapshot.
4. Push to cloud. Run git push. Your work is now on GitHub, backed up.
5. If something breaks, revert. git revert <commit-hash>. Back to the previous snapshot.

That’s it. Three commands cover 90% of what you need.

Common fears (answered)

“I’ll break it.” You can’t. Git is designed for recovery. Even if you delete everything, you can restore it from a previous commit.

“It’s too technical.” The basics aren’t. Commit, push, pull. You don’t need to understand how Git works internally, just like you don’t understand how a car engine works to drive.

“What if I mess up a commit?” Undo it with git revert. What if you push the wrong thing? Revert the push. Git is built for mistakes.

“My files are too large.” Git is fine with files up to a few GB. For larger projects, use Git LFS (Large File Storage), but you won’t need it for most cases.

Next steps

1. Install Git (free, from git-scm.com)
2. Initialize a repo in your project folder: git init
3. Make your first commit: git add . then git commit -m "Initial commit"
4. Create a free GitHub account and push your repo there
5. Now everything is backed up

For detailed commands, see your agent—tell Claude or ChatGPT, “Show me how to use Git,” and it will walk you through it step-by-step.

---

Next in the series

Read [[why SOPs matter before automation]] — Git is how you safely deploy and track your automations.

Also check [[Second Brain in Obsidian]] — keep your notes in Git-tracked folders so they’re backed up too.