Skip to content

01-intro-to-version-control.md

Latest commit

 

History

History
95 lines (67 loc) · 2.87 KB

01-intro-to-version-control.md

File metadata and controls

95 lines (67 loc) · 2.87 KB

Part 1: Introduction to Version Control

What is Version Control? 🤔

Version control is a system that tracks changes to files over time. Think of it like a "time machine" for your code that allows you to:

  • See what changed in your files and when
  • Go back to previous versions if something breaks
  • Work with others without overwriting each other's work
  • Keep a complete history of your project's development

Real-World Analogy 📚

Imagine you're writing a research paper:

Without Version Control:

  • essay.docx
  • essay_final.docx
  • essay_final_v2.docx
  • essay_final_v2_really_final.docx
  • essay_final_v2_really_final_FOR_REAL.docx

Sound familiar? This gets messy quickly!

With Version Control:

  • One file: essay.docx
  • Complete history of all changes
  • Ability to see exactly what changed between versions
  • Easy rollback if you mess something up

Why Do We Need Version Control? 🎯

1. Backup and Recovery

  • Never lose your work again
  • Recover deleted files
  • Restore previous versions

2. Track Changes

  • See what changed, when, and who made the change
  • Understand the evolution of your project

3. Collaboration

  • Multiple people can work on the same project
  • Merge changes automatically
  • Resolve conflicts when people edit the same code

4. Branching

  • Work on features separately
  • Experiment without breaking the main code
  • Switch between different versions easily

5. Documentation

  • Commit messages explain why changes were made
  • Link changes to bug reports or feature requests

Common Version Control Systems 🔧

  • Git (most popular, what we'll learn)
  • Subversion (SVN)
  • Mercurial
  • Bazaar

Git vs. Other Systems 🏆

Git is special because it's:

  • Distributed: Every copy of the code contains the full history
  • Fast: Operations happen locally
  • Flexible: Supports many different workflows
  • Popular: Used by most open-source projects and companies

Key Concepts to Remember 💡

  1. Repository (Repo): A folder that contains your project and its history
  2. Commit: A snapshot of your project at a specific point in time
  3. Branch: A parallel version of your project
  4. Merge: Combining changes from different branches
  5. Remote: A version of your repository stored elsewhere (like GitHub)

What's Next? ➡️

In the next tutorial, we'll dive deeper into why Git specifically has become the standard for version control.

Continue to Part 2: Why Use Git?

Practice Exercise 📝

Before moving on, think about these questions:

  1. Can you think of a time when version control would have saved you from losing work?
  2. What challenges do you face when working on group projects?
  3. How do you currently keep track of different versions of your files?

Write your answers in a text file and save it. We'll use this file in later exercises!