---
title: "Repos and Version Control Explained"
description: "A repository is your project folder tracked by Git, and version control is the safety net that records every change. Learn both in plain language."
type: "fundamental"
locale: "en"
category: "concepts"
canonical: "https://agenticschool.dev/fundamentals/repos-and-version-control"
dateModified: "2026-06-12"
---

# Repos and Version Control Explained

- Category: concepts
- Updated: 2026-06-12
- Keywords: repository, repo, version control, Git, remote repo
- Canonical URL: https://agenticschool.dev/fundamentals/repos-and-version-control
- Locale: en

> A repository is your project folder tracked by Git, and version control is the safety net that records every change. Learn both in plain language.

A repository (or "repo") is your project folder once it is being tracked by a version control tool, and version control is the system that records every change so you can always go back. Put simply, version control is a labelled, unlimited undo history for your whole project, and the repo is the project plus that history. This is the foundation everything else builds on: backups, collaboration and deployment all start with a repo under version control.

## What version control gives you

Version control turns a folder of files into something you can experiment with fearlessly. Every meaningful change is saved as a snapshot you can return to, so a bad edit is never permanent. It also records who changed what and why, which becomes essential the moment more than one person touches the project.

## Local repo vs remote repo

Your repo lives on your computer (the local repo) and usually has a copy online (the remote repo), most often on GitHub. You work locally and "push" your saved changes up to the remote to back them up and share them. The two stay in sync as you push and pull changes.

## Why this matters for shipping

A repo is not just for safety, it is the thing hosting platforms connect to. When your project is a repo on GitHub, a host like Vercel can watch it and redeploy your live site automatically every time you push. So a clean repo under version control is the on-ramp to actually shipping your work.

## Common beginner confusions

A repo can feel like a mysterious special folder, but it is really just your normal project folder with a hidden record of changes attached. You still edit files the same way. People also assume a repo automatically means everything is public or backed up; neither is true until you push to a remote and choose its visibility, and a brand new business repo should default to private. One more point worth internalising early: the history is only as useful as your commits. If you commit rarely with vague messages, the safety net is weak; if you commit often with clear messages, you can step back to any moment with confidence. That single habit is what turns version control from a chore into a genuine superpower.

## FAQ

### What is a repository?

A repository is your project folder once it is tracked by version control, including its full history of changes. People shorten it to "repo". It usually has a local copy and an online copy.

### What is the difference between a repo and version control?

Version control is the system that records changes; the repo is your project plus that recorded history. The repo is the thing; version control is what keeps its timeline.

### Do I need a remote repo?

For backup, collaboration and deployment, yes. A remote repo on GitHub keeps a safe copy off your machine and lets hosting platforms deploy automatically when you push.