Imagine you're writing a big report. You save your first draft as report_v1.docx. Then you make some changes and save it as report_v2.docx. A colleague adds their edits, and now you have report_v2_susan_edits.docx. Before you know it, your folder is a mess of files, and nobody is sure which one is the actual final version. This is a common problem, especially when working on complex projects like software.

Version control systems are tools designed to solve this exact problem. They provide a clean, organized way to track every change made to a project over time. Think of it as a detailed project history that lets you see who changed what, when they changed it, and why. If a new change breaks something, you can easily rewind to a previous working version. It also allows multiple people to work on the same project simultaneously without overwriting each other's work.

Git is the most popular version control system in the world. It's a program that runs on your computer and keeps track of all the changes in your project's files. It's incredibly powerful because it's a distributed system. This means that every person working on the project has a full copy of its entire history on their own machine. This makes it fast and allows people to work offline.

So, what is GitHub? If Git is the tool for tracking changes, GitHub is a website for storing your Git projects and collaborating with others. It's a central place where you can keep a copy of your project, share it with your team, and manage the workflow. You use Git on your computer to save changes, and then you use GitHub to share those changes with everyone else.

To get started with Git and GitHub, you only need to understand a few core ideas. These are the building blocks of every version control workflow.

A repository, or "repo," is the container for your project. It's where all your code, images, documents, and other files live. More importantly, it also contains a hidden directory where Git stores the entire history of every change ever made to those files.

A commit is like saving your game at a checkpoint. When you've made a set of changes you're happy with—like fixing a bug or adding a new feature—you create a commit. Each commit has a unique ID and a descriptive message explaining what you did. This creates a timeline of checkpoints, making it easy to see how the project has evolved.

Finally, there's the concept of branches.

Imagine the main version of your project is a tree trunk. When you want to try out a new idea or work on a feature, you create a branch. This lets you experiment in isolation without disturbing the stable, main version of the project. If your experiment works, you can merge your branch back into the main trunk. If it doesn't, you can simply discard it. This workflow is what makes collaboration safe and organized.

These three concepts—repositories, commits, and branches—are the foundation of using Git. Understanding them allows you to track your work, experiment safely, and collaborate effectively with others.