6 git-remote - Manage set of tracked repositories
12 'git remote' [-v | --verbose]
13 'git remote add' [-t <branch>] [-m <master>] [-f] [--[no-]tags] [--mirror=<fetch|push>] <name> <url>
14 'git remote rename' <old> <new>
15 'git remote remove' <name>
16 'git remote set-head' <name> (-a | --auto | -d | --delete | <branch>)
17 'git remote set-branches' [--add] <name> <branch>...
18 'git remote set-url' [--push] <name> <newurl> [<oldurl>]
19 'git remote set-url --add' [--push] <name> <newurl>
20 'git remote set-url --delete' [--push] <name> <url>
21 'git remote' [-v | --verbose] 'show' [-n] <name>...
22 'git remote prune' [-n | --dry-run] <name>...
23 'git remote' [-v | --verbose] 'update' [-p | --prune] [(<group> | <remote>)...]
28 Manage the set of repositories ("remotes") whose branches you track.
36 Be a little more verbose and show remote url after name.
37 NOTE: This must be placed between `remote` and `subcommand`.
43 With no arguments, shows a list of existing remotes. Several
44 subcommands are available to perform operations on the remotes.
48 Adds a remote named <name> for the repository at
49 <url>. The command `git fetch <name>` can then be used to create and
50 update remote-tracking branches <name>/<branch>.
52 With `-f` option, `git fetch <name>` is run immediately after
53 the remote information is set up.
55 With `--tags` option, `git fetch <name>` imports every tag from the
58 With `--no-tags` option, `git fetch <name>` does not import tags from
59 the remote repository.
61 By default, only tags on fetched branches are imported
62 (see linkgit:git-fetch[1]).
64 With `-t <branch>` option, instead of the default glob
65 refspec for the remote to track all branches under
66 the `refs/remotes/<name>/` namespace, a refspec to track only `<branch>`
67 is created. You can give more than one `-t <branch>` to track
68 multiple branches without grabbing all branches.
70 With `-m <master>` option, a symbolic-ref `refs/remotes/<name>/HEAD` is set
71 up to point at remote's `<master>` branch. See also the set-head command.
73 When a fetch mirror is created with `--mirror=fetch`, the refs will not
74 be stored in the 'refs/remotes/' namespace, but rather everything in
75 'refs/' on the remote will be directly mirrored into 'refs/' in the
76 local repository. This option only makes sense in bare repositories,
77 because a fetch would overwrite any local commits.
79 When a push mirror is created with `--mirror=push`, then `git push`
80 will always behave as if `--mirror` was passed.
84 Rename the remote named <old> to <new>. All remote-tracking branches and
85 configuration settings for the remote are updated.
87 In case <old> and <new> are the same, and <old> is a file under
88 `$GIT_DIR/remotes` or `$GIT_DIR/branches`, the remote is converted to
89 the configuration file format.
94 Remove the remote named <name>. All remote-tracking branches and
95 configuration settings for the remote are removed.
99 Sets or deletes the default branch (i.e. the target of the
100 symbolic-ref `refs/remotes/<name>/HEAD`) for
101 the named remote. Having a default branch for a remote is not required,
102 but allows the name of the remote to be specified in lieu of a specific
103 branch. For example, if the default branch for `origin` is set to
104 `master`, then `origin` may be specified wherever you would normally
105 specify `origin/master`.
107 With `-d` or `--delete`, the symbolic ref `refs/remotes/<name>/HEAD` is deleted.
109 With `-a` or `--auto`, the remote is queried to determine its `HEAD`, then the
110 symbolic-ref `refs/remotes/<name>/HEAD` is set to the same branch. e.g., if the remote
111 `HEAD` is pointed at `next`, "`git remote set-head origin -a`" will set
112 the symbolic-ref `refs/remotes/origin/HEAD` to `refs/remotes/origin/next`. This will
113 only work if `refs/remotes/origin/next` already exists; if not it must be
116 Use `<branch>` to set the symbolic-ref `refs/remotes/<name>/HEAD` explicitly. e.g., "git
117 remote set-head origin master" will set the symbolic-ref `refs/remotes/origin/HEAD` to
118 `refs/remotes/origin/master`. This will only work if
119 `refs/remotes/origin/master` already exists; if not it must be fetched first.
124 Changes the list of branches tracked by the named remote.
125 This can be used to track a subset of the available remote branches
126 after the initial setup for a remote.
128 The named branches will be interpreted as if specified with the
129 `-t` option on the 'git remote add' command line.
131 With `--add`, instead of replacing the list of currently tracked
132 branches, adds to that list.
136 Changes URL remote points to. Sets first URL remote points to matching
137 regex <oldurl> (first URL if no <oldurl> is given) to <newurl>. If
138 <oldurl> doesn't match any URL, error occurs and nothing is changed.
140 With '--push', push URLs are manipulated instead of fetch URLs.
142 With '--add', instead of changing some URL, new URL is added.
144 With '--delete', instead of changing some URL, all URLs matching
145 regex <url> are deleted. Trying to delete all non-push URLs is an
150 Gives some information about the remote <name>.
152 With `-n` option, the remote heads are not queried first with
153 `git ls-remote <name>`; cached information is used instead.
157 Deletes all stale remote-tracking branches under <name>.
158 These stale branches have already been removed from the remote repository
159 referenced by <name>, but are still locally available in
162 With `--dry-run` option, report what branches will be pruned, but do not
167 Fetch updates for a named set of remotes in the repository as defined by
168 remotes.<group>. If a named group is not specified on the command line,
169 the configuration parameter remotes.default will be used; if
170 remotes.default is not defined, all remotes which do not have the
171 configuration parameter remote.<name>.skipDefaultUpdate set to true will
172 be updated. (See linkgit:git-config[1]).
174 With `--prune` option, prune all the remotes that are updated.
180 The remote configuration is achieved using the `remote.origin.url` and
181 `remote.origin.fetch` configuration variables. (See
182 linkgit:git-config[1]).
187 * Add a new remote, fetch, and check out a branch from it
193 origin/HEAD -> origin/master
195 $ git remote add staging git://git.kernel.org/.../gregkh/staging.git
201 From git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging
202 * [new branch] master -> staging/master
203 * [new branch] staging-linus -> staging/staging-linus
204 * [new branch] staging-next -> staging/staging-next
206 origin/HEAD -> origin/master
209 staging/staging-linus
211 $ git checkout -b staging staging/master
215 * Imitate 'git clone' but track only selected branches
221 $ git remote add -f -t master -m master origin git://example.com/git.git/
229 linkgit:git-branch[1]
230 linkgit:git-config[1]
234 Part of the linkgit:git[1] suite