What is a remote?

A remote is simply a copy of your repositoryWhat is repository?A project folder tracked by Git that stores your files along with the complete history of every change, inside a hidden .git directory. Ask AI for more stored elsewhere, usually on the internet. When you clone an existing repository or push your local work to a server, you create this connection.

Your Computer              Remote Server (GitHub)
      |                              |
Local Repo  <--- push --->  Remote Repo
      |        <-- fetch --          |
   Work                         Shared

The most popular remote services

You have several options for hosting your remote repositories:

OriginWhat is origin?The combination of protocol, domain, and port that defines a security boundary in the browser, like https://example.com:443. Ask AI for more: the default remote

When you clone a repositoryWhat is repository?A project folder tracked by Git that stores your files along with the complete history of every change, inside a hidden .git directory. Ask AI for more, Git automatically assigns the name origin to the remote you cloned from. It is just a convention, but everyone follows it:

# This command automatically creates a remote named 'origin'
git clone https://github.com/user/project.git

You can verify this connection:

git remote -v
# origin  https://github.com/user/project.git (fetch)
# origin  https://github.com/user/project.git (push)

The name origin is so universal that every developer immediately understands what you are referring to.

Local vs remote: key differences

The typical remote workflow

Here is what your daily life with Git and remotes looks like:

# 1. Work locally on a branch
git add . && git commit -m "Add login form"

# 2. Push your work to the remote
git push origin my-branch

# 3. Other developers retrieve your changes
git pull origin main

# 4. Collaboration via pull requests, code review
#    (GitHub/GitLab web interface)

Why use remote repositories?

Automatic backup. Your code is safe on a server. If your computer breaks down, you can reclone and pick up exactly where you left off.

Smooth collaboration. Multiple developers can work on the same project without overwriting each other's work. Git manages conflicts intelligently.

Sharing and open source. You can publish your code so others can use it, study it, or contribute to it. It is the heart of open source.

CI/CDWhat is ci/cd?Continuous Integration and Continuous Deployment - automated pipelines that test your code on every push and deploy it when tests pass. Ask AI for more and automation. Remotes can trigger automated tests, deployments, and quality checks on every push.

Git is distributed

This is important: when you clone a remote repositoryWhat is repository?A project folder tracked by Git that stores your files along with the complete history of every change, inside a hidden .git directory. Ask AI for more, you don't just download the current files. You download the entirety of Git history, every commitWhat is commit?A permanent snapshot of your staged changes saved in Git's history, identified by a unique hash and accompanied by a message describing what changed. Ask AI for more, every branch, everything.

# This command downloads all history
git clone https://github.com/user/repo.git

# You can now work offline
# You have the same power as if you were connected

Your first remote

If you start a project locally and want to push it to GitHub:

# 1. Create an empty repository on GitHub (without README)

# 2. In your local project, add the remote
git remote add origin https://github.com/username/my-project.git

# 3. Push your code and set upstream tracking
git push -u origin main

The -u (or --set-upstream) configures your local branch to track the remote branch. After that, you can simply use git push without specifying origin main.

Quick reference