]>
Commit | Line | Data |
---|---|---|
041e69c9 BF |
1 | git-remote(1) |
2 | ============ | |
3 | ||
4 | NAME | |
5 | ---- | |
6 | git-remote - manage set of tracked repositories | |
7 | ||
8 | ||
9 | SYNOPSIS | |
10 | -------- | |
11 | [verse] | |
b1889c36 | 12 | 'git remote' [-v | --verbose] |
a9f5a355 | 13 | 'git remote add' [-t <branch>] [-m <master>] [-f] [--tags|--no-tags] [--mirror=<fetch|push>] <name> <url> |
bf98421a | 14 | 'git remote rename' <old> <new> |
04c2407e | 15 | 'git remote rm' <name> |
4504107d | 16 | 'git remote set-head' <name> (-a | -d | <branch>) |
3d8b6949 | 17 | 'git remote set-branches' <name> [--add] <branch>... |
433f2be1 IL |
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> | |
4504107d | 21 | 'git remote' [-v | --verbose] 'show' [-n] <name> |
04c2407e | 22 | 'git remote prune' [-n | --dry-run] <name> |
0adda936 | 23 | 'git remote' [-v | --verbose] 'update' [-p | --prune] [(<group> | <remote>)...] |
041e69c9 BF |
24 | |
25 | DESCRIPTION | |
26 | ----------- | |
27 | ||
28 | Manage the set of repositories ("remotes") whose branches you track. | |
29 | ||
041e69c9 | 30 | |
459cf2e9 SB |
31 | OPTIONS |
32 | ------- | |
33 | ||
34 | -v:: | |
35 | --verbose:: | |
36 | Be a little more verbose and show remote url after name. | |
4504107d | 37 | NOTE: This must be placed between `remote` and `subcommand`. |
459cf2e9 SB |
38 | |
39 | ||
0f390875 SP |
40 | COMMANDS |
41 | -------- | |
42 | ||
43 | With no arguments, shows a list of existing remotes. Several | |
44 | subcommands are available to perform operations on the remotes. | |
45 | ||
46 | 'add':: | |
47 | ||
48 | Adds a remote named <name> for the repository at | |
041e69c9 BF |
49 | <url>. The command `git fetch <name>` can then be used to create and |
50 | update remote-tracking branches <name>/<branch>. | |
c5ddca1f JH |
51 | + |
52 | With `-f` option, `git fetch <name>` is run immediately after | |
53 | the remote information is set up. | |
54 | + | |
111fb858 ST |
55 | With `--tags` option, `git fetch <name>` imports every tag from the |
56 | remote repository. | |
57 | + | |
58 | With `--no-tags` option, `git fetch <name>` does not import tags from | |
59 | the remote repository. | |
60 | + | |
c5ddca1f JH |
61 | With `-t <branch>` option, instead of the default glob |
62 | refspec for the remote to track all branches under | |
63 | `$GIT_DIR/remotes/<name>/`, a refspec to track only `<branch>` | |
64 | is created. You can give more than one `-t <branch>` to track | |
cf593cc4 | 65 | multiple branches without grabbing all branches. |
c5ddca1f JH |
66 | + |
67 | With `-m <master>` option, `$GIT_DIR/remotes/<name>/HEAD` is set | |
bc14fac8 | 68 | up to point at remote's `<master>` branch. See also the set-head command. |
38944390 | 69 | + |
a9f5a355 JK |
70 | When a fetch mirror is created with `\--mirror=fetch`, the refs will not |
71 | be stored in the 'refs/remotes/' namespace, but rather everything in | |
72 | 'refs/' on the remote will be directly mirrored into 'refs/' in the | |
73 | local repository. This option only makes sense in bare repositories, | |
74 | because a fetch would overwrite any local commits. | |
75 | + | |
76 | When a push mirror is created with `\--mirror=push`, then `git push` | |
77 | will always behave as if `\--mirror` was passed. | |
041e69c9 | 78 | |
bf98421a MV |
79 | 'rename':: |
80 | ||
0e615b25 | 81 | Rename the remote named <old> to <new>. All remote-tracking branches and |
bf98421a | 82 | configuration settings for the remote are updated. |
74443f18 MV |
83 | + |
84 | In case <old> and <new> are the same, and <old> is a file under | |
85 | `$GIT_DIR/remotes` or `$GIT_DIR/branches`, the remote is converted to | |
86 | the configuration file format. | |
bf98421a | 87 | |
1b4cbb5d JB |
88 | 'rm':: |
89 | ||
0e615b25 | 90 | Remove the remote named <name>. All remote-tracking branches and |
1b4cbb5d JB |
91 | configuration settings for the remote are removed. |
92 | ||
bc14fac8 JS |
93 | 'set-head':: |
94 | ||
95 | Sets or deletes the default branch (`$GIT_DIR/remotes/<name>/HEAD`) for | |
96 | the named remote. Having a default branch for a remote is not required, | |
97 | but allows the name of the remote to be specified in lieu of a specific | |
98 | branch. For example, if the default branch for `origin` is set to | |
99 | `master`, then `origin` may be specified wherever you would normally | |
100 | specify `origin/master`. | |
101 | + | |
102 | With `-d`, `$GIT_DIR/remotes/<name>/HEAD` is deleted. | |
103 | + | |
104 | With `-a`, the remote is queried to determine its `HEAD`, then | |
105 | `$GIT_DIR/remotes/<name>/HEAD` is set to the same branch. e.g., if the remote | |
106 | `HEAD` is pointed at `next`, "`git remote set-head origin -a`" will set | |
107 | `$GIT_DIR/refs/remotes/origin/HEAD` to `refs/remotes/origin/next`. This will | |
108 | only work if `refs/remotes/origin/next` already exists; if not it must be | |
109 | fetched first. | |
110 | + | |
111 | Use `<branch>` to set `$GIT_DIR/remotes/<name>/HEAD` explicitly. e.g., "git | |
112 | remote set-head origin master" will set `$GIT_DIR/refs/remotes/origin/HEAD` to | |
113 | `refs/remotes/origin/master`. This will only work if | |
114 | `refs/remotes/origin/master` already exists; if not it must be fetched first. | |
115 | + | |
116 | ||
3d8b6949 JN |
117 | 'set-branches':: |
118 | ||
119 | Changes the list of branches tracked by the named remote. | |
120 | This can be used to track a subset of the available remote branches | |
121 | after the initial setup for a remote. | |
122 | + | |
123 | The named branches will be interpreted as if specified with the | |
124 | `-t` option on the 'git remote add' command line. | |
125 | + | |
126 | With `--add`, instead of replacing the list of currently tracked | |
127 | branches, adds to that list. | |
128 | ||
433f2be1 IL |
129 | 'set-url':: |
130 | ||
131 | Changes URL remote points to. Sets first URL remote points to matching | |
132 | regex <oldurl> (first URL if no <oldurl> is given) to <newurl>. If | |
133 | <oldurl> doesn't match any URL, error occurs and nothing is changed. | |
134 | + | |
135 | With '--push', push URLs are manipulated instead of fetch URLs. | |
136 | + | |
137 | With '--add', instead of changing some URL, new URL is added. | |
138 | + | |
139 | With '--delete', instead of changing some URL, all URLs matching | |
140 | regex <url> are deleted. Trying to delete all non-push URLs is an | |
141 | error. | |
142 | ||
0f390875 | 143 | 'show':: |
041e69c9 | 144 | |
0f390875 | 145 | Gives some information about the remote <name>. |
181ea688 SV |
146 | + |
147 | With `-n` option, the remote heads are not queried first with | |
148 | `git ls-remote <name>`; cached information is used instead. | |
0f390875 SP |
149 | |
150 | 'prune':: | |
151 | ||
8b3f3f84 | 152 | Deletes all stale remote-tracking branches under <name>. |
859607df | 153 | These stale branches have already been removed from the remote repository |
1e592d65 TT |
154 | referenced by <name>, but are still locally available in |
155 | "remotes/<name>". | |
181ea688 | 156 | + |
75f492ac | 157 | With `--dry-run` option, report what branches will be pruned, but do not |
8d767927 | 158 | actually prune them. |
1e592d65 TT |
159 | |
160 | 'update':: | |
161 | ||
1918278e TT |
162 | Fetch updates for a named set of remotes in the repository as defined by |
163 | remotes.<group>. If a named group is not specified on the command line, | |
75f492ac | 164 | the configuration parameter remotes.default will be used; if |
cb5c49b9 | 165 | remotes.default is not defined, all remotes which do not have the |
1918278e | 166 | configuration parameter remote.<name>.skipDefaultUpdate set to true will |
5162e697 | 167 | be updated. (See linkgit:git-config[1]). |
efa54803 FAG |
168 | + |
169 | With `--prune` option, prune all the remotes that are updated. | |
859607df | 170 | |
0f390875 SP |
171 | |
172 | DISCUSSION | |
173 | ---------- | |
174 | ||
041e69c9 BF |
175 | The remote configuration is achieved using the `remote.origin.url` and |
176 | `remote.origin.fetch` configuration variables. (See | |
5162e697 | 177 | linkgit:git-config[1]). |
041e69c9 BF |
178 | |
179 | Examples | |
180 | -------- | |
181 | ||
db554bf0 JH |
182 | * Add a new remote, fetch, and check out a branch from it |
183 | + | |
041e69c9 BF |
184 | ------------ |
185 | $ git remote | |
186 | origin | |
187 | $ git branch -r | |
188 | origin/master | |
8391c60b | 189 | $ git remote add linux-nfs git://linux-nfs.org/pub/linux/nfs-2.6.git |
041e69c9 BF |
190 | $ git remote |
191 | linux-nfs | |
192 | origin | |
193 | $ git fetch | |
194 | * refs/remotes/linux-nfs/master: storing branch 'master' ... | |
195 | commit: bf81b46 | |
196 | $ git branch -r | |
197 | origin/master | |
198 | linux-nfs/master | |
199 | $ git checkout -b nfs linux-nfs/master | |
200 | ... | |
201 | ------------ | |
202 | ||
0b444cdb | 203 | * Imitate 'git clone' but track only selected branches |
db554bf0 JH |
204 | + |
205 | ------------ | |
206 | $ mkdir project.git | |
207 | $ cd project.git | |
208 | $ git init | |
209 | $ git remote add -f -t master -m master origin git://example.com/git.git/ | |
210 | $ git merge origin | |
211 | ------------ | |
212 | ||
213 | ||
56ae8df5 | 214 | SEE ALSO |
041e69c9 | 215 | -------- |
5162e697 DM |
216 | linkgit:git-fetch[1] |
217 | linkgit:git-branch[1] | |
218 | linkgit:git-config[1] | |
041e69c9 | 219 | |
041e69c9 BF |
220 | GIT |
221 | --- | |
9e1f0a85 | 222 | Part of the linkgit:git[1] suite |