Repositories

Local vs Remote

In the Git Basics lesson, you created a repository on your computer. That is a local repo — it lives on your machine, tracks your changes, and nobody else can see it.

A remote repository is a copy that lives on a server somewhere on the internet. This is where collaboration happens, where backups live, and where deployment starts. When you "push" your code, you are sending your commits from local to remote. When you "pull," you are bringing changes from remote to local.

You can work entirely offline with a local repo. The remote is for sharing, backing up, and deploying. Most developers push to a remote at least once a day — often much more.

GitHub Is Not Git

This trips up a lot of people. Git is the version control tool — the software that tracks changes on your computer. GitHub is a website that hosts Git repositories and adds collaboration features on top.

Git was created in 2005. GitHub launched in 2008. Git existed for three years before GitHub was a thing. You can use Git without GitHub. You cannot use GitHub without Git.

GitHub is the most popular host, but it is not the only one. GitLab and Bitbucket do the same thing. Think of Git as email (the protocol) and GitHub as Gmail (one provider). The distinction matters because when someone says "push to GitHub," they mean "use Git to send your commits to a remote repository that happens to be hosted on github.com."

A repository is a project with memory. It knows every version of every file that was ever committed, who changed it, and why.

Cloning

When you want to work on an existing project, you clone it. git clone <url> downloads the entire repository — every file, every commit, the complete history — to your computer.

This is how you get started with other people's code. Found an interesting open source project? Clone it. Your team started a new repo? Clone it. You want to explore how a tool was built? Clone it.

After cloning, you have a fully independent copy. You can edit files, make commits, and experiment without affecting the original. When you are ready to share your changes, you push them back.

# Clone a repository from GitHub
git clone https://github.com/username/project-name.git

# This creates a folder called "project-name" with everything inside
cd project-name
ls -la              # See all the files
git log --oneline   # See the commit history

The README

Every repository should have a README.md file. This is the front door of the project — it tells visitors what it is, how to set it up, and how to use it.

When you visit a repo on GitHub, the README renders automatically below the file list. A good README makes the difference between a project people use and a project people skip.

The .md extension means Markdown — a lightweight formatting language. Headings use #, bold uses text, code uses backticks. You will learn Markdown naturally because it is everywhere: READMEs, documentation, chat apps, and this very curriculum.

Key Files You Will See

Open any well-maintained repository and you will see the same cast of characters:

package.json — The project's identity card. It lists the name, version, dependencies (libraries the project uses), and scripts (commands like "npm run dev" or "npm run build"). If the project runs on Node.js (and most web projects do), this file is the starting point.

.gitignore — A list of files and folders Git should not track. node_modules/ (too large, auto-generated), .env (contains secrets), dist/ (build output). This file keeps your repository clean and safe.

CLAUDE.md — Instructions for AI coding agents. This is a newer convention — it tells tools like Claude Code how the project works, what patterns to follow, and what to avoid. Think of it as onboarding documentation for your AI collaborator.

LICENSE — The legal terms for using the code. MIT means "do whatever you want." GPL means "share your changes too." No license means "technically you cannot use this." For your own projects, MIT is a safe default.

Pushing and Pulling

Once your local repo is connected to a remote (which happens automatically when you clone), two commands keep them in sync:

git push — Send your local commits to the remote. "Here are my changes." If you are working alone, you can push whenever you want. On a team, you push when your work is ready to share.

git pull — Fetch changes from the remote and merge them into your local copy. "Give me the latest." Always pull before you start working if others might have pushed changes. This prevents conflicts.

If you created a repo locally (git init) instead of cloning, you need to connect it to a remote first. GitHub walks you through this when you create a new repository — it gives you the exact commands to run.

# Push your commits to the remote
git push origin main

# Pull the latest changes from the remote
git pull origin main

# Connect a local repo to a new remote
git remote add origin https://github.com/username/my-project.git
git push -u origin main