There are some operations withgit remote, likegit remote -v, that you may use occasionally.

But, the concept of a remote within Git is important and powers many of the other operations.

git remote -v

git remote manages the set of remotes that you are tracking with your local repository.

• git remote -v: List the current remotes associated with the local repository
• git remote add [name] [URL]: Add a remote
• git remote remove [name]: Remove a remote

If you try runninggit remote -v in your repositories, you'll probably see something calledorigin. You may noticeorigin in many messages from Git.origin is the human-friendly name for the URL that the remote repository is stored at. It's like a key-value pair, andorigin is the default.

You may need or want to work with multiple remotes for one local repository. This can be common in open source when a contributor needs to create a fork of a repository to have permission to push changes to the remote.

In this case, it's common to create and clone a fork. Then, the default remote would beorigin, in reference to the fork. To make it easier to pull any changes to update the local copy of the fork from the original repository, many people add the original repository as a remote also. It's typical to name this remoteupstream.

There are four commands within Git that prompt communication with the remote. Unless you are using one of these four commands, all of your work is only happening locally.

• git push
• git clone
• git pull
• git fetch

The concept of branches can be confusing once it is combined with the concept of remotes. Git keeps track of the branches that you work on locally, as well as each of the branches in every remote associated with your local repo.

If you rungit branch --all in your repository, you will notice a long list of branches. The branches that (by default) appear in red are theremote tracking branches. These branches are read-only copies of the branches on the remote. These update every time you rungit fetch orgit pull.

These don't take up much room, so it's okay that Git does this by default. But, these will stack up over time – they are not deleted automatically.

To delete the remote tracking branches that are deleted on the remote, rungit fetch --prune. This is safe to do if you are using GitHub, because branches merged via pull requests can be restored.

When you rungit branch --all, you will also see the local working branches. These can be linked with branches on the remote, or they could exist with no remote counterpart.

• git clone [url]: Clone (download) a repository that already exists on GitHub, including all of the files, branches, and commits.
• git status: Always a good idea, this command shows you what branch you're on, what files are in the working or staging directory, and any other important information.
• git push: Uploads all local branch commits to the remote.
• git pull: Updates your current local working branch with all new commits from the corresponding remote branch on GitHub.git pull is a combination ofgit fetch andgit merge.

Contribute to this article on GitHub.