Skip to content
>devspeak
← glossary
level 3Git & Version Control

Remote

also: remotes, remote repository, git remote

A copy of your Git project stored somewhere else, usually on GitHub, that you send changes to and get changes from.

a bit more technical

A named reference to another copy of the repository, typically hosted on GitHub, GitLab, or Bitbucket. The default remote is usually called origin. Push sends commits to a remote; fetch and pull bring its commits down.

picture it

The family photo album at Grandma's house. You keep your own album at home, and you swap new photos with hers when you visit.

why it matters

Your commits exist only on your computer until they reach the remote. Knowing that tells you whether a change is backed up, shared, or ready to deploy.

what your agent might say
agent
Your local branch is 3 commits ahead of the remote. Nothing has been pushed yet, so these changes only exist on this machine.
how you might use it
you → your agent
Check whether my local main is behind the remote before you start, and pull if needed. Don't push anything without asking me.
common mistake

Assuming your work is saved on GitHub once you commit. Commits stay local until you push them to the remote.

builds on
related