Menu
×
   ❮     
HTML CSS JAVASCRIPT SQL PYTHON JAVA PHP HOW TO W3.CSS C C++ C# BOOTSTRAP REACT MYSQL JQUERY EXCEL XML DJANGO NUMPY PANDAS NODEJS DSA TYPESCRIPT ANGULAR GIT POSTGRESQL MONGODB ASP AI R GO KOTLIN SASS VUE GEN AI SCIPY CYBERSECURITY DATA SCIENCE INTRO TO PROGRAMMING BASH RUST

Git Advanced Remote


What Are Git Remotes?

Remotes are references to remote repositories.

They let you collaborate, fetch, and push code to shared projects on services like GitHub, GitLab, or Bitbucket.


Why Use Multiple Remotes?

You can add more than one remote to your project. This is useful for:

  • Collaborating with different teams (e.g., your fork and the main project)
  • Mirroring repositories
  • Maintaining backups

How to Add a Remote

To add a new remote repository:

Example: Add a Remote

git remote add upstream https://github.com/other/repo.git

How to Remove a Remote

To remove a remote repository:

Example: Remove a Remote

git remote remove upstream

How to Rename a Remote

To change the name of an existing remote (for example, renaming origin to main-origin):

Example: Rename a Remote

git remote rename origin main-origin


How to List All Remotes

See all remotes and their URLs:

Example: List Remotes

git remote -v

How to Show Remote Details

Get detailed information about a specific remote (such as fetch/push URLs and tracked branches):

Example: Show Remote Info

git remote show upstream

How to Fetch from a Remote

Fetch changes from any remote:

Example: Fetch from Upstream

git fetch upstream

How to Push to a Remote

Push your local branch to a specific remote repository:

Example: Push to a Remote

git push upstream main

How to Track a Remote Branch

To set up a local branch to track a branch from a remote:

Example: Track a Remote Branch

git checkout -b new-feature upstream/new-feature

Note: Managing multiple remotes is common in open source projects (e.g., origin for your fork, upstream for the main project).


Troubleshooting and Best Practices

  • If you get "remote not found", check the spelling of the remote name with git remote -v.
  • If fetch or push fails, make sure you have access to the remote repository.
  • Use git remote show <name> to see details and troubleshoot issues.
  • Check your network connection if you cannot reach a remote server.
  • Use clear, descriptive names for remotes (e.g., origin, upstream, backup).
  • Remove unused remotes to keep your project tidy.



×

Contact Sales

If you want to use W3Schools services as an educational institution, team or enterprise, send us an e-mail:
sales@w3schools.com

Report Error

If you want to report an error, or if you want to make a suggestion, send us an e-mail:
help@w3schools.com

W3Schools is optimized for learning and training. Examples might be simplified to improve reading and learning. Tutorials, references, and examples are constantly reviewed to avoid errors, but we cannot warrant full correctness of all content. While using W3Schools, you agree to have read and accepted our terms of use, cookie and privacy policy.

Copyright 1999-2025 by Refsnes Data. All Rights Reserved. W3Schools is Powered by W3.CSS.