Courses/Git/Introduction to Version Control

Lesson 1 • Beginner

Introduction to Version Control 🌿

Discover why version control exists, how Git tracks every change, and set up your first repository — the foundation every developer needs.

What You'll Learn in This Lesson

• What version control is and why every developer uses it
• How Git tracks changes with snapshots (not diffs)
• Git's three areas: Working Directory, Staging, Repository
• Installing and configuring Git for the first time
• Creating your first repository and making your first commit

Running Commands Locally: Git commands run in your terminal (Command Prompt, PowerShell, or Terminal). Our editor simulates the output. Install Git from git-scm.com to follow along.

🎯 Real-World Analogy: Git is like an unlimited undo system for your entire project. Imagine if Google Docs tracked every single change by every collaborator, and you could jump back to any point in time. That's Git — but for code, and it works offline too.

1️⃣ What is Version Control?

Version control is a system that records changes to files over time. Without it, you end up with folders full of "final_v2_ACTUALLY_FINAL.zip" files. Git is the world's most popular version control system — created by Linus Torvalds (the creator of Linux) in 2005. It's distributed, meaning every developer has the full project history on their machine.

Try It: Version Control

See why Git beats the 'rename everything' approach

Try it Yourself »

JavaScript

// What is Git? — Version Control Explained
console.log("=== What is Version Control? ===");
console.log("Version control is a system that tracks changes to files over time.");
console.log("It lets you go back to any previous version, see who changed what,");
console.log("and collaborate with others without overwriting each other's work.");
console.log();

// Simulating a file's version history
console.log("=== A File's History (Like Google Docs) ===");
const history = [
  { version: 1, author: 
...

2️⃣ Installing & Configuring Git

Git is available on every operating system. After installing, you need to configure your name and email — these are embedded in every commit you make so your team knows who changed what.

Try It: Installation & Config

Set up Git on your machine and configure your identity

Try it Yourself »

JavaScript

// Installing and Configuring Git
console.log("=== Installing Git ===");
console.log();
console.log("Windows:");
console.log("  Download from: https://git-scm.com/download/win");
console.log("  Or: winget install Git.Git");
console.log();
console.log("macOS:");
console.log("  xcode-select --install");
console.log("  Or: brew install git");
console.log();
console.log("Linux (Ubuntu/Debian):");
console.log("  sudo apt update && sudo apt install git");
console.log();
console.log("Linux (Fedora):");
...

3️⃣ Git's Three Areas

Understanding Git's three areas is the key to mastering it. The Working Directory is your actual files. The Staging Area is where you prepare changes for a commit. The Repository is the permanent history. Think of it as: edit → stage → commit.

Try It: Three Areas

Watch files move through Working → Staging → Repository

Try it Yourself »

JavaScript

// Git Concepts — The Three Areas
console.log("=== Git's Three Areas ===");
console.log();
console.log("  ┌─────────────┐    git add    ┌──────────────┐   git commit   ┌────────────┐");
console.log("  │  Working     │ ──────────> │  Staging      │ ──────────> │  Repository │");
console.log("  │  Directory   │             │  Area (Index) │             │  (.git)     │");
console.log("  └─────────────┘  <────────── └──────────────┘             └────────────┘");
console.log("                   git r
...

4️⃣ Your First Repository

Use git init to create a new repository, git add to stage files, and git commit to save a snapshot. Use git status constantly — it tells you exactly what's happening.

Try It: First Repository

Create a repo, add files, and make your first commit

Try it Yourself »

JavaScript

// Creating Your First Repository
console.log("=== git init — Start a New Project ===");
console.log();
console.log("  $ mkdir my-project");
console.log("  $ cd my-project");
console.log("  $ git init");
console.log("  Initialized empty Git repository in /my-project/.git/");
console.log();

console.log("=== What git init Creates ===");
console.log("  my-project/");
console.log("  └── .git/             ← Hidden folder (the repository!)");
console.log("      ├── HEAD          ← Points to current b
...

⚠️ Common Mistakes

⚠️

Forgetting git add — Modified files aren't committed until you stage them first. Always git add before git commit.

⚠️

Not setting user name/email — Git will warn you on your first commit. Set these globally with git config --global.

💡

Pro Tip: Run git status after every command when learning. It's the best way to understand what Git is doing.

📋 Quick Reference — Essential Git Commands

Command	What It Does
git init	Create a new repository
git status	See what's changed
git add file	Stage a file for commit
git commit -m "msg"	Save a snapshot
git log --oneline	View commit history
git config --global	Set global settings

🎉 Lesson Complete!

You now understand version control and can create your first Git repository. Next, we'll master the daily workflow: clone, add, and commit!

Introduction to Version Control 🌿

What You'll Learn in This Lesson

1️⃣ What is Version Control?

Try It: Version Control

2️⃣ Installing & Configuring Git

Try It: Installation & Config

3️⃣ Git's Three Areas

Try It: Three Areas

4️⃣ Your First Repository

Try It: First Repository

⚠️ Common Mistakes

📋 Quick Reference — Essential Git Commands

🎉 Lesson Complete!

Cookie & Privacy Settings