With no arguments, shows a list of existing remotes. Several
subcommands are available to perform operations on the remotes.
Adds a remote named <name> for the repository at <url>. The
command git fetch <name> can then be used to create and update
remote-tracking branches <name>/<branch>.
With -f option, git fetch <name> is run immediately after the
remote information is set up.
With --tags option, git fetch <name> imports every tag from the
With --no-tags option, git fetch <name> does not import tags from
the remote repository.
By default, only tags on fetched branches are imported (see
With -t <branch> option, instead of the default glob refspec for
the remote to track all branches under the refs/remotes/<name>/
namespace, a refspec to track only <branch> is created. You can
give more than one -t <branch> to track multiple branches without
grabbing all branches.
With -m <master> option, a symbolic-ref refs/remotes/<name>/HEAD
is set up to point at remote’s <master> branch. See also the
When a fetch mirror is created with --mirror=fetch, the refs will
not be stored in the refs/remotes/ namespace, but rather
everything in refs/ on the remote will be directly mirrored into
refs/ in the local repository. This option only makes sense in
bare repositories, because a fetch would overwrite any local
When a push mirror is created with --mirror=push, then git push
will always behave as if --mirror was passed.
Rename the remote named <old> to <new>. All remote-tracking
branches and configuration settings for the remote are updated.
In case <old> and <new> are the same, and <old> is a file under
$GIT_DIR/remotes or $GIT_DIR/branches, the remote is converted to
the configuration file format.
Remove the remote named <name>. All remote-tracking branches and
configuration settings for the remote are removed.
Sets or deletes the default branch (i.e. the target of the
symbolic-ref refs/remotes/<name>/HEAD) for the named remote.
Having a default branch for a remote is not required, but allows
the name of the remote to be specified in lieu of a specific
branch. For example, if the default branch for origin is set to
master, then origin may be specified wherever you would normally
With -d or --delete, the symbolic ref refs/remotes/<name>/HEAD is
With -a or --auto, the remote is queried to determine its HEAD,
then the symbolic-ref refs/remotes/<name>/HEAD is set to the same
branch. e.g., if the remote HEAD is pointed at next, "git remoteset-head origin -a" will set the symbolic-ref
refs/remotes/origin/HEAD to refs/remotes/origin/next. This will
only work if refs/remotes/origin/next already exists; if not it
must be fetched first.
Use <branch> to set the symbolic-ref refs/remotes/<name>/HEAD
explicitly. e.g., "git remote set-head origin master" will set
the symbolic-ref refs/remotes/origin/HEAD to
refs/remotes/origin/master. This will only work if
refs/remotes/origin/master already exists; if not it must be
Changes the list of branches tracked by the named remote. This
can be used to track a subset of the available remote branches
after the initial setup for a remote.
The named branches will be interpreted as if specified with the
-t option on the git remote add command line.
With --add, instead of replacing the list of currently tracked
branches, adds to that list.
Retrieves the URLs for a remote. Configurations for insteadOf and
pushInsteadOf are expanded here. By default, only the first URL
With --push, push URLs are queried rather than fetch URLs.
With --all, all URLs for the remote will be listed.
Changes URLs for the remote. Sets first URL for remote <name>
that matches regex <oldurl> (first URL if no <oldurl> is given)
to <newurl>. If <oldurl> doesn’t match any URL, an error occurs
and nothing is changed.
With --push, push URLs are manipulated instead of fetch URLs.
With --add, instead of changing existing URLs, new URL is added.
With --delete, instead of changing existing URLs, all URLs
matching regex <url> are deleted for remote <name>. Trying to
delete all non-push URLs is an error.
Note that the push URL and the fetch URL, even though they can be
set differently, must still refer to the same place. What you
pushed to the push URL should be what you would see if you
immediately fetched from the fetch URL. If you are trying to
fetch from one place (e.g. your upstream) and push to another
(e.g. your publishing repository), use two separate remotes.
Gives some information about the remote <name>.
With -n option, the remote heads are not queried first with gitls-remote <name>; cached information is used instead.
Deletes all stale remote-tracking branches under <name>. These
stale branches have already been removed from the remote
repository referenced by <name>, but are still locally available
With --dry-run option, report what branches will be pruned, but
do not actually prune them.
Fetch updates for a named set of remotes in the repository as
defined by remotes.<group>. If a named group is not specified on
the command line, the configuration parameter remotes.default
will be used; if remotes.default is not defined, all remotes
which do not have the configuration parameter
remote.<name>.skipDefaultUpdate set to true will be updated. (See
With --prune option, prune all the remotes that are updated.
This page is part of the git (Git distributed version control system)
project. Information about the project can be found at
⟨http://git-scm.com/⟩. If you have a bug report for this manual page,
see ⟨http://git-scm.com/community⟩. This page was obtained from the
project's upstream Git repository ⟨https://github.com/git/git.git⟩ on
2017-03-13. If you discover any rendering problems in this HTML ver‐
sion of the page, or you believe there is a better or more up-to-date
source for the page, or you have corrections or improvements to the
information in this COLOPHON (which is not part of the original man‐
ual page), send a mail to email@example.com
Git 184.108.40.2067.g2949358 07/16/2016 GIT-REMOTE(1)