Remote Repositories

So far, Git can work completely on your machine.

But teams need a shared place where code can be stored, reviewed, and pulled by others.

That shared place is usually a remote repository.

GitHub is one popular place to host remote Git repositories.

Local vs remote

Your local commits do not automatically appear on GitHub.

You push them.

GitHub changes do not automatically appear on your machine.

You fetch or pull them.

What is origin?

When you clone a repository from GitHub, Git usually names that remote origin.

Example:

git clone https://github.com/example/api.git

Inside that cloned project:

git remote -v

You may see:

origin  https://github.com/example/api.git (fetch)
origin  https://github.com/example/api.git (push)

origin is just a default remote name. It is not magic.

Why remotes matter

Remote repositories allow:

• backup of code,
• team collaboration,
• pull requests,
• code review,
• CI/CD,
• release workflows,
• open source contribution.

Without remotes, Git is still useful for personal history, but collaboration becomes harder.

Basic remote commands

Add a remote:

git remote add origin https://github.com/user/project.git

Push your branch:

git push origin main

Fetch remote updates:

git fetch origin

Pull remote updates into your branch:

git pull origin main

Common mistake

Beginners often think GitHub has the "real" code and local Git is just a copy.

Git is distributed.

Your local repository has real commit history too. GitHub is a shared remote copy with collaboration features.

Interview answer

A remote repository is a Git repository hosted outside my machine, commonly on GitHub. I use remotes to share commits with others. push sends local commits to the remote, fetch downloads remote history without merging, and pull fetches and integrates remote changes into the current branch.