blob: fad983e297514da7e847196b0375e3254fdf235d [file] [log] [blame]
git-remote - manage set of tracked repositories
'git remote' [-v | --verbose]
'git remote add' [-t <branch>] [-m <master>] [-f] [--mirror] <name> <url>
'git remote rename' <old> <new>
'git remote rm' <name>
'git remote show' [-n] <name>
'git remote prune' [-n | --dry-run] <name>
'git remote update' [group]
Manage the set of repositories ("remotes") whose branches you track.
Be a little more verbose and show remote url after name.
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 `-t <branch>` option, instead of the default glob
refspec for the remote to track all branches under
`$GIT_DIR/remotes/<name>/`, 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, `$GIT_DIR/remotes/<name>/HEAD` is set
up to point at remote's `<master>` branch instead of whatever
branch the `HEAD` at the remote repository actually points at.
In mirror mode, enabled with `\--mirror`, the refs will not be stored
in the 'refs/remotes/' namespace, but in 'refs/heads/'. This option
only makes sense in bare repositories. If a remote uses mirror
mode, furthermore, `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.
Gives some information about the remote <name>.
With `-n` option, the remote heads are not queried first with
`git ls-remote <name>`; cached information is used instead.
Deletes all stale tracking branches under <name>.
These stale branches have already been removed from the remote repository
referenced by <name>, but are still locally available in
With `--dry-run` option, report what branches will be pruned, but do no
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 get 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 linkgit:git-config[1]).
The remote configuration is achieved using the `remote.origin.url` and
`remote.origin.fetch` configuration variables. (See
* Add a new remote, fetch, and check out a branch from it
$ git remote
$ git branch -r
$ git remote add linux-nfs git://
$ git remote
$ git fetch
* refs/remotes/linux-nfs/master: storing branch 'master' ...
commit: bf81b46
$ git branch -r
$ git checkout -b nfs linux-nfs/master
* Imitate 'git-clone' but track only selected branches
$ mkdir project.git
$ cd project.git
$ git init
$ git remote add -f -t master -m master origin git://
$ git merge origin
Written by Junio Hamano
Documentation by J. Bruce Fields and the git-list <>.
Part of the linkgit:git[1] suite