Git for Non-Developers

The Time Machine for Your Files

Imagine if every time you saved a document, your computer took a picture of everything in your project at that exact moment — and you could flip back through those pictures anytime you wanted. That's what Git does. It's a tool that keeps a full history of every version of your project, so you can go back in time if something breaks, try new ideas without fear, and work with other people without stepping on each other's toes.

Most people save files like this: you open a document, make changes, and hit Save. The old version is gone. Git changes that completely. Every time you save a snapshot in Git, it remembers exactly what changed and when. Messed up two weeks from now? Jump right back to today's version with one command.

Git isn't just for programmers. Writers use it to track manuscript versions. Designers use it to keep a history of their work. Small teams use it to coordinate without sending files back and forth over email.

Collaboration Without Catastrophe

Here's a story everyone knows: you have a project, you make a copy to share with someone, they make changes, you make changes, and suddenly you have fourteen versions named "final," "final_v2," and "final_ACTUAL_REAL_final." Someone accidentally deleted the best version. Nobody knows what's what.

Git solves this at the root. Instead of passing files around, everyone works from the same shared history. Each person makes their own separate branch — like a parallel universe of the project — does their work, and then their branch gets merged back in. Nobody overwrites anyone else's work. The full history exists for everyone.

The Four-Step Save

Git has a simple vocabulary. Once you understand these four actions, you understand the core of how it works:

Think of it like packing a suitcase. You make changes to your project (filling your suitcase with stuff). You stage changes (deciding what goes in). You commit (zipping it up with a label). And you push (sending it somewhere safe). Three key concepts tie it all together:

A Typical Git Workflow

Here's how someone might use Git to save their work on a website project. You don't need to type all of this manually — GitHub Desktop and tools like Cursor can handle the commands for you. But understanding what each step does helps a lot:

# Start tracking a project with Git
git init

# See what files have changed
git status

# Stage specific files to include in the next snapshot
git add index.html
git add styles.css

# Commit — save a snapshot with a note
git commit -m "Added new header and colors"

# Send your commits up to GitHub
git push origin main

# Start a new branch to try a risky experiment
git checkout -b new-feature

# Merge your experiment back in when it's ready
git checkout main
git merge new-feature

Notice -m "Added new header and colors" — every commit gets a short note so you can understand your history at a glance. Writing clear commit messages like "Fixed the broken button" is much more useful than "updated file5.html."

Knowledge Check

Test what you learned with this quick quiz.