Branches are just duplicating a Google Doc. Commits are checkpoints. Push and pull are syncing to the cloud. You don't memorize git commands — Claude Code handles them for you.

Git Is Google Docs Version History, But Better

If you've ever used Google Docs, you already understand the core idea behind git. Google Docs automatically saves every change and lets you go back to any previous version. Git does the same thing for code — but you decide when to save (called a 'commit') and you can add a note about what you changed and why.

The good news: you don't need to memorize git commands. Claude Code handles all the git operations for you. But understanding the concepts will help you work more confidently and communicate with engineers on your team.

The Four Concepts You Actually Need

1. Commits = Checkpoints

A commit is a snapshot of your project at a specific moment. Think of it like hitting 'Save' in a video game — you can always go back to that checkpoint if things go wrong. Each commit has a message describing what changed, like 'Added conversion rate chart to dashboard' or 'Fixed the date filter bug.'

2. Branches = Duplicating a Google Doc

A branch is like making a copy of your Google Doc to try something new without messing up the original. The 'main' branch is your live, working version. When you want to add a feature or experiment, you create a new branch, make your changes there, and only merge it back into main when you're confident it works.

3. Push = Upload to the Cloud

When you 'push,' you're uploading your local changes to GitHub (or another cloud service). It's like syncing a local file to Google Drive. This means your work is backed up and other people can see it.

4. Pull = Download the Latest

When you 'pull,' you're downloading the latest changes from the cloud to your computer. If a teammate made changes, pulling brings their updates to your local copy. It's like refreshing a shared Google Doc.

git-concepts.shbash

# You don't type these — Claude Code does them for you.
# But here's what's happening behind the scenes:

# Save a checkpoint
git add .
git commit -m "Added campaign ROI chart to dashboard"

# Upload your changes to GitHub
git push

# Download your teammate's latest changes
git pull

# Create a new branch to try something
git checkout -b add-date-filter

# Switch back to the main version
git checkout main

Manual Workflow

Without version control: You name files 'dashboard-v1.py', 'dashboard-v2-final.py', 'dashboard-v2-ACTUALLY-final.py'. You accidentally overwrite something. You can't remember what you changed last Tuesday. Your teammate edits the same file and somebody's work gets lost.

With AI

With git: Every change is tracked with a timestamp and description. You can see exactly what changed and when. You can undo any change. Multiple people can work on the same project without conflicts. And Claude Code handles all of this for you.

Time saved: Hours of confusion and lost work, permanently

Letting Claude Code Handle Git

Here's the best part: Claude Code understands git natively. You can just tell it what you want in plain English:

'Save my progress and push it to GitHub' — Claude Code commits and pushes
'Create a new branch for the date filter feature' — Claude Code creates and switches to a new branch
'I messed something up, can you undo my last change?' — Claude Code reverts the commit
'Show me what I changed since yesterday' — Claude Code shows the diff

Pro Tip

Even though Claude Code handles git commands for you, commit frequently with descriptive messages. A good rule of thumb: commit every time you finish a small, working piece. 'Added the KPI row to the dashboard' is a good commit. 'Updated stuff' is not. Your future self will thank you when you need to find or undo something specific.

GitHub: Your Project's Home Base

GitHub is where your code lives in the cloud. Think of it as Google Drive for code projects. Creating an account is free, and Claude Code can set up a new repository for you with a single prompt. Once your project is on GitHub, it's backed up, shareable, and you can even set up automatic deployments so that every time you push changes, your dashboard or tool updates automatically.

Try It Yourself

Take one of the projects you've built in previous lessons (the dashboard, the automated report, or the internal tool) and ask Claude Code to set up git and push it to GitHub. Practice making a change, committing it, and pushing it. Then make another change and practice reverting it.

Initialize git in this project, create a GitHub repository called 'marketing-dashboard', and push all my code there. Then show me the status so I can see everything is synced.

Git Basics — Version Control for Non-Engineers