Managing remote repositories

When collaborating on any project managed with Git, you will interact often with a constant set of other repositories. For example, using the integration-manager workflow will involve (at least) the canonical blessed repository of a project. In many cases, you will interact with more than one remote repository.

Git allows us to save the information about a remote repository (or just remote for short) in the config file by giving it a nickname (a shorthand name). This configuration can be managed with the git remote command.

Legacy mechanisms for storing remote repository information

There are also two legacy mechanisms to store the information about remote repositories.

This first is a named file in .git/remotes—the name of this file will be the nickname of the remote. This file can contain information about the URL or URLs, and fetch and push refspecs.

The second is a named file in .git/branches—the name of this file will also...