DEV Community

MysticMc
MysticMc

Posted on

Git vs. GitHub: The 5-minute guide for absolute beginners

#git #github #versioncontrol

If you're new to coding, you've probably heard people say:

"Just push it to GitHub."

Or:

"Make sure you commit your changes."

And if you're like most beginners, you quietly nodded… while secretly thinking: "Wait… are Git and GitHub the same thing?"

You are not alone. This is the most common confusion for new developers.

Here's the truth in one sentence:

Git is the tool. GitHub is the website where you put the tool's work.

Let me explain in 5 minutes (or less).

The 2-Second Summary

Git GitHub
What is it? A program on your computer A website in the cloud
What does it do? Tracks changes to your code Hosts your Git repositories online
Do you need internet? ❌ No (works offline) ✅ Yes
Is it free? ✅ Yes (always) ✅ Yes for public repos (paid for private team features)
Who makes it? Linus Torvalds (same guy who made Linux) Microsoft (acquired in 2018)

The Analogy: Writing a Book 📚

Imagine you're writing a novel.

Git is your "Save & Track Changes" button (locally)

You write on your laptop. Every time you hit Save, Git takes a snapshot. You can:

  • Go back to page 37 from yesterday.
  • See exactly what words you deleted.
  • Try a crazy experiment (kill off the main character!) without losing the original.

All of this happens on your own computer. No internet required.

GitHub is the library (cloud hosting)

Now you want to:

  • Share your book with a co-author.
  • Show your progress to the world.
  • Make sure your laptop exploding doesn't erase 6 months of work.

So you upload your Git project to GitHub. It's like putting your book in a public library (or a private locker). Others can read it, suggest changes, or download their own copy.

This requires the internet.

What Git actually does (the 3 commands you need)

Git tracks your code using repositories (folders with a special .git hidden folder). Here's the basic workflow:

# 1. You change a file (index.html)
# 2. You stage it (tell Git "hey, pay attention to this")
git add index.html

# 3. You commit it (take a permanent snapshot)
git commit -m "Fixed the broken button"

# 4. Repeat 100 times. You now have 100 snapshots.
Enter fullscreen mode Exit fullscreen mode

That's it. Git never touches the internet. It's just a smart "undo" button on steroids.

What GitHub actually does (the 3 things you need)

GitHub takes your local Git repository and:

  1. Hosts it online – So you don't lose it if your computer dies.
  2. Lets others collaborate – Multiple people can push changes to the same repo.
  3. Adds project management tools – Issue tracking, pull requests, code reviews, CI/CD. 
# After you've committed locally, you send it to GitHub:
git push origin main

# Now your code is on GitHub.com. Anyone can see it (if public).
Enter fullscreen mode Exit fullscreen mode

Common beginner mistakes (and how to fix them)

❌ "I deleted my project folder. But I pushed to GitHub yesterday, so I'm safe!"

Not exactly. GitHub has your code, but you still need to git clone it back down. It's not magic. You have to explicitly download it.

✅ Fix: git clone https://github.com/yourname/yourrepo.git

❌ "I made changes on GitHub.com (edited a file in the browser) and now my local version is different."

This creates a merge conflict. GitHub has version A, your laptop has version B. Git doesn't know which is correct.

✅ Fix: git pull origin main before you start working. Always.

❌ "Git and GitHub are the same company, right?"

Nope. Git was created in 2005 by Linus Torvalds (Linux guy). GitHub launched in 2008 as a startup that built a website around Git. Microsoft bought GitHub for $7.5 billion in 2018.

Alternatives to GitHub:

  • GitLab (self-hosted option)
  • Bitbucket (Atlassian)
  • SourceForge (the old guard)

But they all use Git underneath. Git is the engine. GitHub is just one car brand.

Visual timeline of a real workflow 

[Your laptop]                    [GitHub cloud]
     |                                |
     | 1. Write code                  |
     | 2. git add .                   |
     | 3. git commit -m "..."         |
     |                                |
     | 4. git push -----------------> | 5. Code appears online
     |                                |
     | 6. Friend clones or forks      |
     |    the repo from GitHub         |
     |                                |
     | 7. git pull <------------------| 8. Get their changes
     |                                |
Enter fullscreen mode Exit fullscreen mode

Internet is only needed for steps 4, 6, and 8. Everything else works offline.

Why you need BOTH (not one or the other)

If you ONLY use Git (no GitHub) If you ONLY use GitHub (no Git locally)
✅ You have version history ✅ Your code is backed up online
✅ You can undo mistakes ✅ Others can see your work
❌ No cloud backup ❌ You need internet for everything
❌ Hard to collaborate ❌ You can't work offline
❌ Computer dies = code dies ❌ You're just editing files in a browser (not real dev work)

The pro move: Use Git locally for daily work. Push to GitHub periodically for backup and collaboration.

Your first 10 minutes with Git + GitHub

Here's a concrete starter plan:

Step 1: Install Git

  • Mac: brew install git or download from git-scm.com
  • Windows: Download from git-scm.com (Git Bash included)
  • Linux: sudo apt install git (Ubuntu/Debian)

Step 2: Configure your identity (one time) 

git config --global user.name "Your Name"
git config --global user.email "your@email.com"
Enter fullscreen mode Exit fullscreen mode

Step 3: Create a GitHub account

Go to github.com and sign up (free).

Step 4: Create a repo on GitHub

Click the "+" icon → "New repository" → name it "my-first-repo" → check "Add a README" → Create.

Step 5: Clone it to your computer 

git clone https://github.com/yourusername/my-first-repo.git
cd my-first-repo
Enter fullscreen mode Exit fullscreen mode

Step 6: Make a change

Open the README.md file. Add a line: "I understand Git vs. GitHub now!"

Step 7: Commit and push 

git add README.md
git commit -m "Added my realization"
git push origin main
Enter fullscreen mode Exit fullscreen mode

Step 8: Refresh GitHub.com

See your change live. 🎉

The "Aha!" moment explained

Here's how you'll know you truly understand:

Git is to GitHub as your camera roll is to Instagram.

  • Your camera roll (Git) stores all your photos locally. You can edit, delete, and organize them offline.
  • Instagram (GitHub) is where you upload some of those photos to share with the world.
  • You can delete Instagram and still have your photos. You can delete your camera roll and lose everything (unless Instagram had a copy).

Never trust the cloud as your only copy. Always have Git locally.

FAQ (from actual beginners)

"Do I need to learn Git before using GitHub?"

Yes, but only the basics (add, commit, push, pull, clone). You can learn those in 30 minutes.

"Can I use GitHub without using Git?"

Technically yes (you can edit files directly on GitHub.com). But that's like editing a website using only Notepad. Professionals don't do this.

"What's a 'fork'?"

A copy of someone else's GitHub repository that lives under your GitHub account. You can modify it without affecting the original.

"What's a 'pull request'?"

You saying: "Hey, I changed your code. Here are my changes. Want to pull them into your project?"

"Is GitHub safe for proprietary code?"

Yes, but you need a private repository (paid on some plans, free on GitHub for small teams). For top-secret stuff, companies use self-hosted GitLab.

Final cheat sheet (bookmark this) 

# Git commands (work offline)
git init                 # Start tracking a folder
git add file.txt         # Stage a file
git commit -m "message"  # Take a snapshot
git log                  # See your history
git diff                 # See what changed
git checkout [commitID]  # Go back in time

# GitHub commands (need internet)
git clone [url]          # Download a repo from GitHub
git push origin main     # Upload your commits to GitHub
git pull origin main     # Download latest changes from GitHub
git remote -v            # See which GitHub URL you're connected to
Enter fullscreen mode Exit fullscreen mode

Your turn

Now go do this:

  1. Open your terminal.
  2. Create a folder called git-practice.
  3. Run git init inside it.
  4. Create a file called hello.txt.
  5. Run git add . then git commit -m "first commit".
  6. Go to GitHub, create a new repo (don't add a README this time).
  7. Follow the "...or push an existing repository from the command line" instructions.

You just became a real developer. 🚀

Found this helpful? Leave a comment with your biggest Git or GitHub facepalm moment. We've all been there.

Want more beginner guides? Drop a follow and I'll cover branching, merging, and fixing merge conflicts next.

Top comments (0)