INSCITR
← Back to Notes

Git for Humans: A Beginner's Guide

June 1, 2026

Plain-language Git workflow, branching, and undo commands for beginners.

git devops

Think of Git as a time machine for your project folder. Instead of saving files as project_final.doc, project_final_v2.doc, and project_REALLY_final.doc, Git remembers every version of every file you’ve ever saved, allowing you to jump back in time if you make a mistake.

📚 The Vocabulary

  • Repository (or “Repo”): Your project folder that Git is watching.
  • Commit: A “save point” or a snapshot in time.
  • Staging Area: The “waiting room” for changes before they are saved.
  • Remote: A copy of your project stored on the internet (like GitHub).

Part 1: The Daily Workflow

This is the “loop” you will perform almost every single day while working on a project.

1. git init (The Birth)

git init

What it does: Tells Git, “Start watching this folder.” Non-technical explanation: Imagine buying a new notebook and drawing a little “Git” logo on the first page so you remember to keep track of everything written inside. You only do this once per project.

2. git status (The Check-up)

git status

What it does: Shows you what has changed. Non-technical explanation: Asking Git, “Hey, what’s the current situation? Have I changed anything since we last talked?” It will tell you which files are new or modified.

3. git add (The Staging Area)

git add <filename>

What it does: Prepares a specific file to be saved. Non-technical explanation: Imagine you are packing a box for shipping. git add is the act of picking up an item and putting it inside the box. The items are in the box, but you haven’t taped it shut yet.

Tip — stage everything in the folder:

git add .

4. git commit (The Save Point)

git commit -m "A helpful note"

What it does: Permanently saves your staged changes into the history. Non-technical explanation: This is taping the box shut and writing a label on it like “Added the logo” or “Fixed the typo in the header.” Once you commit, that moment in time is recorded forever.

5. git push (The Cloud Upload)

git push

What it does: Sends your saved changes to a remote server (like GitHub). Non-technical explanation: Taking your labeled box and putting it on a delivery truck so it travels to a warehouse (GitHub) where others can see it or you can access it from another computer.

Part 2: Working on New Ideas (Branching)

Branches allow you to step out of the “main” timeline to try something risky without breaking your working project.

1. git branch (Creating a Parallel Universe)

git branch <name>

Non-technical explanation: Imagine you have a finished book, but you want to see what happens if the main character dies instead of surviving. You create a “branch” version of the book so you can write that new ending without ruining your original copy.

2. git checkout (Traveling between timelines)

git checkout <name>

Non-technical explanation: This is the act of physically switching your view from the “Main” timeline to your “Experimental” timeline.

3. git merge (Merging Timelines)

git merge <name>

Non-technical explanation: If your experiment was a success, merge pulls all those new changes back into your main project. It’s like taking the pages from your experimental notebook and taping them back into the original notebook.

Part 3: Oops! I Made a Mistake (Rolling Back)

1. “I messed up the file, but I haven’t ‘added’ it to the box yet.”

git checkout -- <filename>

Explanation: This acts like an “Undo” button. It reverts the file back to exactly how it looked at your last save point (the last commit).

2. “I added a file to the box, but I don’t want it in this shipment.”

git reset <filename>

Explanation: This is like reaching into the box and taking an item back out before you tape it shut. The file stays on your computer, but it’s no longer “staged” for the next save.

3. “I need to go back to a version from yesterday.”

git log
git checkout <commit-id>

Explanation: git log shows you a list of all your past “labeled boxes” with ID numbers. By using checkout, you are essentially teleporting your entire project folder back to exactly how it looked at that specific ID number.

💡 Git Pearls (Pro Tips & Random Knowledge)

  • The .gitignore Trick: This is a special file where you list files you never want Git to track (like passwords or huge temporary folders).

    • The Slash Secret: There is a big difference between /portfolio/ and portfolio/ in your .gitignore.
      • /portfolio/ (with a leading slash) means: “Only ignore the folder named ‘portfolio’ if it is sitting right in the main root folder.”
      • portfolio/ (no leading slash) means: “Ignore any folder named ‘portfolio’ anywhere in the entire project, even if it’s buried deep inside other folders.”

  • The “Commit Small, Commit Often” Rule: Don’t wait until you’ve finished a 10-hour coding session to commit. If you make a small change that works, commit it! It makes it much easier to find where a mistake happened later.

  • git diff (The X-Ray): Before you stage changes, compare your work:

git diff

Then stage when ready:

git add .

It shows you exactly which lines were added or deleted. It’s like looking through an X-ray machine to make sure there are no broken bones in your code before you “package” it.

  • The .git Folder is the Brain: When you run git init, a hidden folder named .git is created. This folder contains the entire history of your project. If you delete this folder, your “time machine” is destroyed, and your project becomes just a regular, un-tracked folder again.

  • Don’t Panic: Almost nothing in Git is truly permanent unless you are specifically deleting the history. If you feel lost, git status is almost always the best first step to see where you are standing.

← Back to Notes