6 git - the stupid content tracker
12 'git' [--version] [--help] [-C <path>] [-c <name>=<value>]
13 [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
14 [-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
15 [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
20 Git is a fast, scalable, distributed revision control system with an
21 unusually rich command set that provides both high-level operations
22 and full access to internals.
24 See linkgit:gittutorial[7] to get started, then see
25 linkgit:giteveryday[7] for a useful minimum set of
26 commands. The link:user-manual.html[Git User's Manual] has a more
27 in-depth introduction.
29 After you mastered the basic concepts, you can come back to this
30 page to learn what commands Git offers. You can learn more about
31 individual Git commands with "git help command". linkgit:gitcli[7]
32 manual page gives you an overview of the command-line command syntax.
34 A formatted and hyperlinked copy of the latest Git documentation
35 can be viewed at `https://git.github.io/htmldocs/git.html`.
41 You are reading the documentation for the latest (possibly
42 unreleased) version of Git, that is available from the 'master'
43 branch of the `git.git` repository.
44 Documentation for older releases are available here:
46 * link:v2.10.2/git.html[documentation for release 2.10.2]
49 link:RelNotes/2.10.2.txt[2.10.2],
50 link:RelNotes/2.10.1.txt[2.10.1],
51 link:RelNotes/2.10.0.txt[2.10].
53 * link:v2.9.4/git.html[documentation for release 2.9.4]
56 link:RelNotes/2.9.4.txt[2.9.4],
57 link:RelNotes/2.9.3.txt[2.9.3],
58 link:RelNotes/2.9.2.txt[2.9.2],
59 link:RelNotes/2.9.1.txt[2.9.1],
60 link:RelNotes/2.9.0.txt[2.9].
62 * link:v2.8.5/git.html[documentation for release 2.8.5]
65 link:RelNotes/2.8.5.txt[2.8.5],
66 link:RelNotes/2.8.4.txt[2.8.4],
67 link:RelNotes/2.8.3.txt[2.8.3],
68 link:RelNotes/2.8.2.txt[2.8.2],
69 link:RelNotes/2.8.1.txt[2.8.1],
70 link:RelNotes/2.8.0.txt[2.8].
72 * link:v2.7.5/git.html[documentation for release 2.7.5]
75 link:RelNotes/2.7.5.txt[2.7.5],
76 link:RelNotes/2.7.4.txt[2.7.4],
77 link:RelNotes/2.7.3.txt[2.7.3],
78 link:RelNotes/2.7.2.txt[2.7.2],
79 link:RelNotes/2.7.1.txt[2.7.1],
80 link:RelNotes/2.7.0.txt[2.7].
82 * link:v2.6.7/git.html[documentation for release 2.6.7]
85 link:RelNotes/2.6.7.txt[2.6.7],
86 link:RelNotes/2.6.6.txt[2.6.6],
87 link:RelNotes/2.6.5.txt[2.6.5],
88 link:RelNotes/2.6.4.txt[2.6.4],
89 link:RelNotes/2.6.3.txt[2.6.3],
90 link:RelNotes/2.6.2.txt[2.6.2],
91 link:RelNotes/2.6.1.txt[2.6.1],
92 link:RelNotes/2.6.0.txt[2.6].
94 * link:v2.5.6/git.html[documentation for release 2.5.6]
97 link:RelNotes/2.5.6.txt[2.5.6],
98 link:RelNotes/2.5.5.txt[2.5.5],
99 link:RelNotes/2.5.4.txt[2.5.4],
100 link:RelNotes/2.5.3.txt[2.5.3],
101 link:RelNotes/2.5.2.txt[2.5.2],
102 link:RelNotes/2.5.1.txt[2.5.1],
103 link:RelNotes/2.5.0.txt[2.5].
105 * link:v2.4.12/git.html[documentation for release 2.4.12]
108 link:RelNotes/2.4.12.txt[2.4.12],
109 link:RelNotes/2.4.11.txt[2.4.11],
110 link:RelNotes/2.4.10.txt[2.4.10],
111 link:RelNotes/2.4.9.txt[2.4.9],
112 link:RelNotes/2.4.8.txt[2.4.8],
113 link:RelNotes/2.4.7.txt[2.4.7],
114 link:RelNotes/2.4.6.txt[2.4.6],
115 link:RelNotes/2.4.5.txt[2.4.5],
116 link:RelNotes/2.4.4.txt[2.4.4],
117 link:RelNotes/2.4.3.txt[2.4.3],
118 link:RelNotes/2.4.2.txt[2.4.2],
119 link:RelNotes/2.4.1.txt[2.4.1],
120 link:RelNotes/2.4.0.txt[2.4].
122 * link:v2.3.10/git.html[documentation for release 2.3.10]
125 link:RelNotes/2.3.10.txt[2.3.10],
126 link:RelNotes/2.3.9.txt[2.3.9],
127 link:RelNotes/2.3.8.txt[2.3.8],
128 link:RelNotes/2.3.7.txt[2.3.7],
129 link:RelNotes/2.3.6.txt[2.3.6],
130 link:RelNotes/2.3.5.txt[2.3.5],
131 link:RelNotes/2.3.4.txt[2.3.4],
132 link:RelNotes/2.3.3.txt[2.3.3],
133 link:RelNotes/2.3.2.txt[2.3.2],
134 link:RelNotes/2.3.1.txt[2.3.1],
135 link:RelNotes/2.3.0.txt[2.3].
137 * link:v2.2.3/git.html[documentation for release 2.2.3]
140 link:RelNotes/2.2.3.txt[2.2.3],
141 link:RelNotes/2.2.2.txt[2.2.2],
142 link:RelNotes/2.2.1.txt[2.2.1],
143 link:RelNotes/2.2.0.txt[2.2].
145 * link:v2.1.4/git.html[documentation for release 2.1.4]
148 link:RelNotes/2.1.4.txt[2.1.4],
149 link:RelNotes/2.1.3.txt[2.1.3],
150 link:RelNotes/2.1.2.txt[2.1.2],
151 link:RelNotes/2.1.1.txt[2.1.1],
152 link:RelNotes/2.1.0.txt[2.1].
154 * link:v2.0.5/git.html[documentation for release 2.0.5]
157 link:RelNotes/2.0.5.txt[2.0.5],
158 link:RelNotes/2.0.4.txt[2.0.4],
159 link:RelNotes/2.0.3.txt[2.0.3],
160 link:RelNotes/2.0.2.txt[2.0.2],
161 link:RelNotes/2.0.1.txt[2.0.1],
162 link:RelNotes/2.0.0.txt[2.0.0].
164 * link:v1.9.5/git.html[documentation for release 1.9.5]
167 link:RelNotes/1.9.5.txt[1.9.5],
168 link:RelNotes/1.9.4.txt[1.9.4],
169 link:RelNotes/1.9.3.txt[1.9.3],
170 link:RelNotes/1.9.2.txt[1.9.2],
171 link:RelNotes/1.9.1.txt[1.9.1],
172 link:RelNotes/1.9.0.txt[1.9.0].
174 * link:v1.8.5.6/git.html[documentation for release 1.8.5.6]
177 link:RelNotes/1.8.5.6.txt[1.8.5.6],
178 link:RelNotes/1.8.5.5.txt[1.8.5.5],
179 link:RelNotes/1.8.5.4.txt[1.8.5.4],
180 link:RelNotes/1.8.5.3.txt[1.8.5.3],
181 link:RelNotes/1.8.5.2.txt[1.8.5.2],
182 link:RelNotes/1.8.5.1.txt[1.8.5.1],
183 link:RelNotes/1.8.5.txt[1.8.5].
185 * link:v1.8.4.5/git.html[documentation for release 1.8.4.5]
188 link:RelNotes/1.8.4.5.txt[1.8.4.5],
189 link:RelNotes/1.8.4.4.txt[1.8.4.4],
190 link:RelNotes/1.8.4.3.txt[1.8.4.3],
191 link:RelNotes/1.8.4.2.txt[1.8.4.2],
192 link:RelNotes/1.8.4.1.txt[1.8.4.1],
193 link:RelNotes/1.8.4.txt[1.8.4].
195 * link:v1.8.3.4/git.html[documentation for release 1.8.3.4]
198 link:RelNotes/1.8.3.4.txt[1.8.3.4],
199 link:RelNotes/1.8.3.3.txt[1.8.3.3],
200 link:RelNotes/1.8.3.2.txt[1.8.3.2],
201 link:RelNotes/1.8.3.1.txt[1.8.3.1],
202 link:RelNotes/1.8.3.txt[1.8.3].
204 * link:v1.8.2.3/git.html[documentation for release 1.8.2.3]
207 link:RelNotes/1.8.2.3.txt[1.8.2.3],
208 link:RelNotes/1.8.2.2.txt[1.8.2.2],
209 link:RelNotes/1.8.2.1.txt[1.8.2.1],
210 link:RelNotes/1.8.2.txt[1.8.2].
212 * link:v1.8.1.6/git.html[documentation for release 1.8.1.6]
215 link:RelNotes/1.8.1.6.txt[1.8.1.6],
216 link:RelNotes/1.8.1.5.txt[1.8.1.5],
217 link:RelNotes/1.8.1.4.txt[1.8.1.4],
218 link:RelNotes/1.8.1.3.txt[1.8.1.3],
219 link:RelNotes/1.8.1.2.txt[1.8.1.2],
220 link:RelNotes/1.8.1.1.txt[1.8.1.1],
221 link:RelNotes/1.8.1.txt[1.8.1].
223 * link:v1.8.0.3/git.html[documentation for release 1.8.0.3]
226 link:RelNotes/1.8.0.3.txt[1.8.0.3],
227 link:RelNotes/1.8.0.2.txt[1.8.0.2],
228 link:RelNotes/1.8.0.1.txt[1.8.0.1],
229 link:RelNotes/1.8.0.txt[1.8.0].
231 * link:v1.7.12.4/git.html[documentation for release 1.7.12.4]
234 link:RelNotes/1.7.12.4.txt[1.7.12.4],
235 link:RelNotes/1.7.12.3.txt[1.7.12.3],
236 link:RelNotes/1.7.12.2.txt[1.7.12.2],
237 link:RelNotes/1.7.12.1.txt[1.7.12.1],
238 link:RelNotes/1.7.12.txt[1.7.12].
240 * link:v1.7.11.7/git.html[documentation for release 1.7.11.7]
243 link:RelNotes/1.7.11.7.txt[1.7.11.7],
244 link:RelNotes/1.7.11.6.txt[1.7.11.6],
245 link:RelNotes/1.7.11.5.txt[1.7.11.5],
246 link:RelNotes/1.7.11.4.txt[1.7.11.4],
247 link:RelNotes/1.7.11.3.txt[1.7.11.3],
248 link:RelNotes/1.7.11.2.txt[1.7.11.2],
249 link:RelNotes/1.7.11.1.txt[1.7.11.1],
250 link:RelNotes/1.7.11.txt[1.7.11].
252 * link:v1.7.10.5/git.html[documentation for release 1.7.10.5]
255 link:RelNotes/1.7.10.5.txt[1.7.10.5],
256 link:RelNotes/1.7.10.4.txt[1.7.10.4],
257 link:RelNotes/1.7.10.3.txt[1.7.10.3],
258 link:RelNotes/1.7.10.2.txt[1.7.10.2],
259 link:RelNotes/1.7.10.1.txt[1.7.10.1],
260 link:RelNotes/1.7.10.txt[1.7.10].
262 * link:v1.7.9.7/git.html[documentation for release 1.7.9.7]
265 link:RelNotes/1.7.9.7.txt[1.7.9.7],
266 link:RelNotes/1.7.9.6.txt[1.7.9.6],
267 link:RelNotes/1.7.9.5.txt[1.7.9.5],
268 link:RelNotes/1.7.9.4.txt[1.7.9.4],
269 link:RelNotes/1.7.9.3.txt[1.7.9.3],
270 link:RelNotes/1.7.9.2.txt[1.7.9.2],
271 link:RelNotes/1.7.9.1.txt[1.7.9.1],
272 link:RelNotes/1.7.9.txt[1.7.9].
274 * link:v1.7.8.6/git.html[documentation for release 1.7.8.6]
277 link:RelNotes/1.7.8.6.txt[1.7.8.6],
278 link:RelNotes/1.7.8.5.txt[1.7.8.5],
279 link:RelNotes/1.7.8.4.txt[1.7.8.4],
280 link:RelNotes/1.7.8.3.txt[1.7.8.3],
281 link:RelNotes/1.7.8.2.txt[1.7.8.2],
282 link:RelNotes/1.7.8.1.txt[1.7.8.1],
283 link:RelNotes/1.7.8.txt[1.7.8].
285 * link:v1.7.7.7/git.html[documentation for release 1.7.7.7]
288 link:RelNotes/1.7.7.7.txt[1.7.7.7],
289 link:RelNotes/1.7.7.6.txt[1.7.7.6],
290 link:RelNotes/1.7.7.5.txt[1.7.7.5],
291 link:RelNotes/1.7.7.4.txt[1.7.7.4],
292 link:RelNotes/1.7.7.3.txt[1.7.7.3],
293 link:RelNotes/1.7.7.2.txt[1.7.7.2],
294 link:RelNotes/1.7.7.1.txt[1.7.7.1],
295 link:RelNotes/1.7.7.txt[1.7.7].
297 * link:v1.7.6.6/git.html[documentation for release 1.7.6.6]
300 link:RelNotes/1.7.6.6.txt[1.7.6.6],
301 link:RelNotes/1.7.6.5.txt[1.7.6.5],
302 link:RelNotes/1.7.6.4.txt[1.7.6.4],
303 link:RelNotes/1.7.6.3.txt[1.7.6.3],
304 link:RelNotes/1.7.6.2.txt[1.7.6.2],
305 link:RelNotes/1.7.6.1.txt[1.7.6.1],
306 link:RelNotes/1.7.6.txt[1.7.6].
308 * link:v1.7.5.4/git.html[documentation for release 1.7.5.4]
311 link:RelNotes/1.7.5.4.txt[1.7.5.4],
312 link:RelNotes/1.7.5.3.txt[1.7.5.3],
313 link:RelNotes/1.7.5.2.txt[1.7.5.2],
314 link:RelNotes/1.7.5.1.txt[1.7.5.1],
315 link:RelNotes/1.7.5.txt[1.7.5].
317 * link:v1.7.4.5/git.html[documentation for release 1.7.4.5]
320 link:RelNotes/1.7.4.5.txt[1.7.4.5],
321 link:RelNotes/1.7.4.4.txt[1.7.4.4],
322 link:RelNotes/1.7.4.3.txt[1.7.4.3],
323 link:RelNotes/1.7.4.2.txt[1.7.4.2],
324 link:RelNotes/1.7.4.1.txt[1.7.4.1],
325 link:RelNotes/1.7.4.txt[1.7.4].
327 * link:v1.7.3.5/git.html[documentation for release 1.7.3.5]
330 link:RelNotes/1.7.3.5.txt[1.7.3.5],
331 link:RelNotes/1.7.3.4.txt[1.7.3.4],
332 link:RelNotes/1.7.3.3.txt[1.7.3.3],
333 link:RelNotes/1.7.3.2.txt[1.7.3.2],
334 link:RelNotes/1.7.3.1.txt[1.7.3.1],
335 link:RelNotes/1.7.3.txt[1.7.3].
337 * link:v1.7.2.5/git.html[documentation for release 1.7.2.5]
340 link:RelNotes/1.7.2.5.txt[1.7.2.5],
341 link:RelNotes/1.7.2.4.txt[1.7.2.4],
342 link:RelNotes/1.7.2.3.txt[1.7.2.3],
343 link:RelNotes/1.7.2.2.txt[1.7.2.2],
344 link:RelNotes/1.7.2.1.txt[1.7.2.1],
345 link:RelNotes/1.7.2.txt[1.7.2].
347 * link:v1.7.1.4/git.html[documentation for release 1.7.1.4]
350 link:RelNotes/1.7.1.4.txt[1.7.1.4],
351 link:RelNotes/1.7.1.3.txt[1.7.1.3],
352 link:RelNotes/1.7.1.2.txt[1.7.1.2],
353 link:RelNotes/1.7.1.1.txt[1.7.1.1],
354 link:RelNotes/1.7.1.txt[1.7.1].
356 * link:v1.7.0.9/git.html[documentation for release 1.7.0.9]
359 link:RelNotes/1.7.0.9.txt[1.7.0.9],
360 link:RelNotes/1.7.0.8.txt[1.7.0.8],
361 link:RelNotes/1.7.0.7.txt[1.7.0.7],
362 link:RelNotes/1.7.0.6.txt[1.7.0.6],
363 link:RelNotes/1.7.0.5.txt[1.7.0.5],
364 link:RelNotes/1.7.0.4.txt[1.7.0.4],
365 link:RelNotes/1.7.0.3.txt[1.7.0.3],
366 link:RelNotes/1.7.0.2.txt[1.7.0.2],
367 link:RelNotes/1.7.0.1.txt[1.7.0.1],
368 link:RelNotes/1.7.0.txt[1.7.0].
370 * link:v1.6.6.3/git.html[documentation for release 1.6.6.3]
373 link:RelNotes/1.6.6.3.txt[1.6.6.3],
374 link:RelNotes/1.6.6.2.txt[1.6.6.2],
375 link:RelNotes/1.6.6.1.txt[1.6.6.1],
376 link:RelNotes/1.6.6.txt[1.6.6].
378 * link:v1.6.5.9/git.html[documentation for release 1.6.5.9]
381 link:RelNotes/1.6.5.9.txt[1.6.5.9],
382 link:RelNotes/1.6.5.8.txt[1.6.5.8],
383 link:RelNotes/1.6.5.7.txt[1.6.5.7],
384 link:RelNotes/1.6.5.6.txt[1.6.5.6],
385 link:RelNotes/1.6.5.5.txt[1.6.5.5],
386 link:RelNotes/1.6.5.4.txt[1.6.5.4],
387 link:RelNotes/1.6.5.3.txt[1.6.5.3],
388 link:RelNotes/1.6.5.2.txt[1.6.5.2],
389 link:RelNotes/1.6.5.1.txt[1.6.5.1],
390 link:RelNotes/1.6.5.txt[1.6.5].
392 * link:v1.6.4.5/git.html[documentation for release 1.6.4.5]
395 link:RelNotes/1.6.4.5.txt[1.6.4.5],
396 link:RelNotes/1.6.4.4.txt[1.6.4.4],
397 link:RelNotes/1.6.4.3.txt[1.6.4.3],
398 link:RelNotes/1.6.4.2.txt[1.6.4.2],
399 link:RelNotes/1.6.4.1.txt[1.6.4.1],
400 link:RelNotes/1.6.4.txt[1.6.4].
402 * link:v1.6.3.4/git.html[documentation for release 1.6.3.4]
405 link:RelNotes/1.6.3.4.txt[1.6.3.4],
406 link:RelNotes/1.6.3.3.txt[1.6.3.3],
407 link:RelNotes/1.6.3.2.txt[1.6.3.2],
408 link:RelNotes/1.6.3.1.txt[1.6.3.1],
409 link:RelNotes/1.6.3.txt[1.6.3].
412 link:RelNotes/1.6.2.5.txt[1.6.2.5],
413 link:RelNotes/1.6.2.4.txt[1.6.2.4],
414 link:RelNotes/1.6.2.3.txt[1.6.2.3],
415 link:RelNotes/1.6.2.2.txt[1.6.2.2],
416 link:RelNotes/1.6.2.1.txt[1.6.2.1],
417 link:RelNotes/1.6.2.txt[1.6.2].
419 * link:v1.6.1.3/git.html[documentation for release 1.6.1.3]
422 link:RelNotes/1.6.1.3.txt[1.6.1.3],
423 link:RelNotes/1.6.1.2.txt[1.6.1.2],
424 link:RelNotes/1.6.1.1.txt[1.6.1.1],
425 link:RelNotes/1.6.1.txt[1.6.1].
427 * link:v1.6.0.6/git.html[documentation for release 1.6.0.6]
430 link:RelNotes/1.6.0.6.txt[1.6.0.6],
431 link:RelNotes/1.6.0.5.txt[1.6.0.5],
432 link:RelNotes/1.6.0.4.txt[1.6.0.4],
433 link:RelNotes/1.6.0.3.txt[1.6.0.3],
434 link:RelNotes/1.6.0.2.txt[1.6.0.2],
435 link:RelNotes/1.6.0.1.txt[1.6.0.1],
436 link:RelNotes/1.6.0.txt[1.6.0].
438 * link:v1.5.6.6/git.html[documentation for release 1.5.6.6]
441 link:RelNotes/1.5.6.6.txt[1.5.6.6],
442 link:RelNotes/1.5.6.5.txt[1.5.6.5],
443 link:RelNotes/1.5.6.4.txt[1.5.6.4],
444 link:RelNotes/1.5.6.3.txt[1.5.6.3],
445 link:RelNotes/1.5.6.2.txt[1.5.6.2],
446 link:RelNotes/1.5.6.1.txt[1.5.6.1],
447 link:RelNotes/1.5.6.txt[1.5.6].
449 * link:v1.5.5.6/git.html[documentation for release 1.5.5.6]
452 link:RelNotes/1.5.5.6.txt[1.5.5.6],
453 link:RelNotes/1.5.5.5.txt[1.5.5.5],
454 link:RelNotes/1.5.5.4.txt[1.5.5.4],
455 link:RelNotes/1.5.5.3.txt[1.5.5.3],
456 link:RelNotes/1.5.5.2.txt[1.5.5.2],
457 link:RelNotes/1.5.5.1.txt[1.5.5.1],
458 link:RelNotes/1.5.5.txt[1.5.5].
460 * link:v1.5.4.7/git.html[documentation for release 1.5.4.7]
463 link:RelNotes/1.5.4.7.txt[1.5.4.7],
464 link:RelNotes/1.5.4.6.txt[1.5.4.6],
465 link:RelNotes/1.5.4.5.txt[1.5.4.5],
466 link:RelNotes/1.5.4.4.txt[1.5.4.4],
467 link:RelNotes/1.5.4.3.txt[1.5.4.3],
468 link:RelNotes/1.5.4.2.txt[1.5.4.2],
469 link:RelNotes/1.5.4.1.txt[1.5.4.1],
470 link:RelNotes/1.5.4.txt[1.5.4].
472 * link:v1.5.3.8/git.html[documentation for release 1.5.3.8]
475 link:RelNotes/1.5.3.8.txt[1.5.3.8],
476 link:RelNotes/1.5.3.7.txt[1.5.3.7],
477 link:RelNotes/1.5.3.6.txt[1.5.3.6],
478 link:RelNotes/1.5.3.5.txt[1.5.3.5],
479 link:RelNotes/1.5.3.4.txt[1.5.3.4],
480 link:RelNotes/1.5.3.3.txt[1.5.3.3],
481 link:RelNotes/1.5.3.2.txt[1.5.3.2],
482 link:RelNotes/1.5.3.1.txt[1.5.3.1],
483 link:RelNotes/1.5.3.txt[1.5.3].
485 * link:v1.5.2.5/git.html[documentation for release 1.5.2.5]
488 link:RelNotes/1.5.2.5.txt[1.5.2.5],
489 link:RelNotes/1.5.2.4.txt[1.5.2.4],
490 link:RelNotes/1.5.2.3.txt[1.5.2.3],
491 link:RelNotes/1.5.2.2.txt[1.5.2.2],
492 link:RelNotes/1.5.2.1.txt[1.5.2.1],
493 link:RelNotes/1.5.2.txt[1.5.2].
495 * link:v1.5.1.6/git.html[documentation for release 1.5.1.6]
498 link:RelNotes/1.5.1.6.txt[1.5.1.6],
499 link:RelNotes/1.5.1.5.txt[1.5.1.5],
500 link:RelNotes/1.5.1.4.txt[1.5.1.4],
501 link:RelNotes/1.5.1.3.txt[1.5.1.3],
502 link:RelNotes/1.5.1.2.txt[1.5.1.2],
503 link:RelNotes/1.5.1.1.txt[1.5.1.1],
504 link:RelNotes/1.5.1.txt[1.5.1].
506 * link:v1.5.0.7/git.html[documentation for release 1.5.0.7]
509 link:RelNotes/1.5.0.7.txt[1.5.0.7],
510 link:RelNotes/1.5.0.6.txt[1.5.0.6],
511 link:RelNotes/1.5.0.5.txt[1.5.0.5],
512 link:RelNotes/1.5.0.3.txt[1.5.0.3],
513 link:RelNotes/1.5.0.2.txt[1.5.0.2],
514 link:RelNotes/1.5.0.1.txt[1.5.0.1],
515 link:RelNotes/1.5.0.txt[1.5.0].
517 * documentation for release link:v1.4.4.4/git.html[1.4.4.4],
518 link:v1.3.3/git.html[1.3.3],
519 link:v1.2.6/git.html[1.2.6],
520 link:v1.0.13/git.html[1.0.13].
529 Prints the Git suite version that the 'git' program came from.
532 Prints the synopsis and a list of the most commonly used
533 commands. If the option `--all` or `-a` is given then all
534 available commands are printed. If a Git command is named this
535 option will bring up the manual page for that command.
537 Other options are available to control how the manual page is
538 displayed. See linkgit:git-help[1] for more information,
539 because `git --help ...` is converted internally into `git
543 Run as if git was started in '<path>' instead of the current working
544 directory. When multiple `-C` options are given, each subsequent
545 non-absolute `-C <path>` is interpreted relative to the preceding `-C
548 This option affects options that expect path name like `--git-dir` and
549 `--work-tree` in that their interpretations of the path names would be
550 made relative to the working directory caused by the `-C` option. For
551 example the following invocations are equivalent:
553 git --git-dir=a.git --work-tree=b -C c status
554 git --git-dir=c/a.git --work-tree=c/b status
557 Pass a configuration parameter to the command. The value
558 given will override values from configuration files.
559 The <name> is expected in the same format as listed by
560 'git config' (subkeys separated by dots).
562 Note that omitting the `=` in `git -c foo.bar ...` is allowed and sets
563 `foo.bar` to the boolean true value (just like `[foo]bar` would in a
564 config file). Including the equals but with an empty value (like `git -c
565 foo.bar= ...`) sets `foo.bar` to the empty string.
567 --exec-path[=<path>]::
568 Path to wherever your core Git programs are installed.
569 This can also be controlled by setting the GIT_EXEC_PATH
570 environment variable. If no path is given, 'git' will print
571 the current setting and then exit.
574 Print the path, without trailing slash, where Git's HTML
575 documentation is installed and exit.
578 Print the manpath (see `man(1)`) for the man pages for
579 this version of Git and exit.
582 Print the path where the Info files documenting this
583 version of Git are installed and exit.
587 Pipe all output into 'less' (or if set, $PAGER) if standard
588 output is a terminal. This overrides the `pager.<cmd>`
589 configuration options (see the "Configuration Mechanism" section
593 Do not pipe Git output into a pager.
596 Set the path to the repository. This can also be controlled by
597 setting the `GIT_DIR` environment variable. It can be an absolute
598 path or relative path to current working directory.
601 Set the path to the working tree. It can be an absolute path
602 or a path relative to the current working directory.
603 This can also be controlled by setting the GIT_WORK_TREE
604 environment variable and the core.worktree configuration
605 variable (see core.worktree in linkgit:git-config[1] for a
606 more detailed discussion).
609 Set the Git namespace. See linkgit:gitnamespaces[7] for more
610 details. Equivalent to setting the `GIT_NAMESPACE` environment
614 Treat the repository as a bare repository. If GIT_DIR
615 environment is not set, it is set to the current working
618 --no-replace-objects::
619 Do not use replacement refs to replace Git objects. See
620 linkgit:git-replace[1] for more information.
622 --literal-pathspecs::
623 Treat pathspecs literally (i.e. no globbing, no pathspec magic).
624 This is equivalent to setting the `GIT_LITERAL_PATHSPECS` environment
628 Add "glob" magic to all pathspec. This is equivalent to setting
629 the `GIT_GLOB_PATHSPECS` environment variable to `1`. Disabling
630 globbing on individual pathspecs can be done using pathspec
634 Add "literal" magic to all pathspec. This is equivalent to setting
635 the `GIT_NOGLOB_PATHSPECS` environment variable to `1`. Enabling
636 globbing on individual pathspecs can be done using pathspec
640 Add "icase" magic to all pathspec. This is equivalent to setting
641 the `GIT_ICASE_PATHSPECS` environment variable to `1`.
646 We divide Git into high level ("porcelain") commands and low level
647 ("plumbing") commands.
649 High-level commands (porcelain)
650 -------------------------------
652 We separate the porcelain commands into the main commands and some
653 ancillary user utilities.
655 Main porcelain commands
656 ~~~~~~~~~~~~~~~~~~~~~~~
658 include::cmds-mainporcelain.txt[]
664 include::cmds-ancillarymanipulators.txt[]
668 include::cmds-ancillaryinterrogators.txt[]
671 Interacting with Others
672 ~~~~~~~~~~~~~~~~~~~~~~~
674 These commands are to interact with foreign SCM and with other
675 people via patch over e-mail.
677 include::cmds-foreignscminterface.txt[]
680 Low-level commands (plumbing)
681 -----------------------------
683 Although Git includes its
684 own porcelain layer, its low-level commands are sufficient to support
685 development of alternative porcelains. Developers of such porcelains
686 might start by reading about linkgit:git-update-index[1] and
687 linkgit:git-read-tree[1].
689 The interface (input, output, set of options and the semantics)
690 to these low-level commands are meant to be a lot more stable
691 than Porcelain level commands, because these commands are
692 primarily for scripted use. The interface to Porcelain commands
693 on the other hand are subject to change in order to improve the
696 The following description divides
697 the low-level commands into commands that manipulate objects (in
698 the repository, index, and working tree), commands that interrogate and
699 compare objects, and commands that move objects and references between
703 Manipulation commands
704 ~~~~~~~~~~~~~~~~~~~~~
706 include::cmds-plumbingmanipulators.txt[]
709 Interrogation commands
710 ~~~~~~~~~~~~~~~~~~~~~~
712 include::cmds-plumbinginterrogators.txt[]
714 In general, the interrogate commands do not touch the files in
718 Synching repositories
719 ~~~~~~~~~~~~~~~~~~~~~
721 include::cmds-synchingrepositories.txt[]
723 The following are helper commands used by the above; end users
724 typically do not use them directly.
726 include::cmds-synchelpers.txt[]
729 Internal helper commands
730 ~~~~~~~~~~~~~~~~~~~~~~~~
732 These are internal helper commands used by other commands; end
733 users typically do not use them directly.
735 include::cmds-purehelpers.txt[]
738 Configuration Mechanism
739 -----------------------
741 Git uses a simple text format to store customizations that are per
742 repository and are per user. Such a configuration file may look
747 # A '#' or ';' character indicates a comment.
752 ; Don't trust file modes
757 name = "Junio C Hamano"
758 email = "gitster@pobox.com"
762 Various commands read from the configuration file and adjust
763 their operation accordingly. See linkgit:git-config[1] for a
764 list and more details about the configuration mechanism.
767 Identifier Terminology
768 ----------------------
770 Indicates the object name for any type of object.
773 Indicates a blob object name.
776 Indicates a tree object name.
779 Indicates a commit object name.
782 Indicates a tree, commit or tag object name. A
783 command that takes a <tree-ish> argument ultimately wants to
784 operate on a <tree> object but automatically dereferences
785 <commit> and <tag> objects that point at a <tree>.
788 Indicates a commit or tag object name. A
789 command that takes a <commit-ish> argument ultimately wants to
790 operate on a <commit> object but automatically dereferences
791 <tag> objects that point at a <commit>.
794 Indicates that an object type is required.
795 Currently one of: `blob`, `tree`, `commit`, or `tag`.
798 Indicates a filename - almost always relative to the
799 root of the tree structure `GIT_INDEX_FILE` describes.
803 Any Git command accepting any <object> can also use the following
807 indicates the head of the current branch.
811 (i.e. a `refs/tags/<tag>` reference).
815 (i.e. a `refs/heads/<head>` reference).
817 For a more complete list of ways to spell object names, see
818 "SPECIFYING REVISIONS" section in linkgit:gitrevisions[7].
821 File/Directory Structure
822 ------------------------
824 Please see the linkgit:gitrepository-layout[5] document.
826 Read linkgit:githooks[5] for more details about each hook.
828 Higher level SCMs may provide and manage additional information in the
834 Please see linkgit:gitglossary[7].
837 Environment Variables
838 ---------------------
839 Various Git commands use the following environment variables:
843 These environment variables apply to 'all' core Git commands. Nb: it
844 is worth noting that they may be used/overridden by SCMS sitting above
845 Git so take care if using a foreign front-end.
848 This environment allows the specification of an alternate
849 index file. If not specified, the default of `$GIT_DIR/index`
852 `GIT_INDEX_VERSION`::
853 This environment variable allows the specification of an index
854 version for new repositories. It won't affect existing index
855 files. By default index file version 2 or 3 is used. See
856 linkgit:git-update-index[1] for more information.
858 `GIT_OBJECT_DIRECTORY`::
859 If the object storage directory is specified via this
860 environment variable then the sha1 directories are created
861 underneath - otherwise the default `$GIT_DIR/objects`
864 `GIT_ALTERNATE_OBJECT_DIRECTORIES`::
865 Due to the immutable nature of Git objects, old objects can be
866 archived into shared, read-only directories. This variable
867 specifies a ":" separated (on Windows ";" separated) list
868 of Git object directories which can be used to search for Git
869 objects. New objects will not be written to these directories.
872 If the `GIT_DIR` environment variable is set then it
873 specifies a path to use instead of the default `.git`
874 for the base of the repository.
875 The `--git-dir` command-line option also sets this value.
878 Set the path to the root of the working tree.
879 This can also be controlled by the `--work-tree` command-line
880 option and the core.worktree configuration variable.
883 Set the Git namespace; see linkgit:gitnamespaces[7] for details.
884 The `--namespace` command-line option also sets this value.
886 `GIT_CEILING_DIRECTORIES`::
887 This should be a colon-separated list of absolute paths. If
888 set, it is a list of directories that Git should not chdir up
889 into while looking for a repository directory (useful for
890 excluding slow-loading network directories). It will not
891 exclude the current working directory or a GIT_DIR set on the
892 command line or in the environment. Normally, Git has to read
893 the entries in this list and resolve any symlink that
894 might be present in order to compare them with the current
895 directory. However, if even this access is slow, you
896 can add an empty entry to the list to tell Git that the
897 subsequent entries are not symlinks and needn't be resolved;
899 `GIT_CEILING_DIRECTORIES=/maybe/symlink::/very/slow/non/symlink`.
901 `GIT_DISCOVERY_ACROSS_FILESYSTEM`::
902 When run in a directory that does not have ".git" repository
903 directory, Git tries to find such a directory in the parent
904 directories to find the top of the working tree, but by default it
905 does not cross filesystem boundaries. This environment variable
906 can be set to true to tell Git not to stop at filesystem
907 boundaries. Like `GIT_CEILING_DIRECTORIES`, this will not affect
908 an explicit repository directory set via `GIT_DIR` or on the
912 If this variable is set to a path, non-worktree files that are
913 normally in $GIT_DIR will be taken from this path
914 instead. Worktree-specific files such as HEAD or index are
915 taken from $GIT_DIR. See linkgit:gitrepository-layout[5] and
916 linkgit:git-worktree[1] for
917 details. This variable has lower precedence than other path
918 variables such as GIT_INDEX_FILE, GIT_OBJECT_DIRECTORY...
925 `GIT_COMMITTER_NAME`::
926 `GIT_COMMITTER_EMAIL`::
927 `GIT_COMMITTER_DATE`::
929 see linkgit:git-commit-tree[1]
934 Only valid setting is "--unified=??" or "-u??" to set the
935 number of context lines shown when a unified diff is created.
936 This takes precedence over any "-U" or "--unified" option
937 value passed on the Git diff command line.
939 `GIT_EXTERNAL_DIFF`::
940 When the environment variable `GIT_EXTERNAL_DIFF` is set, the
941 program named by it is called, instead of the diff invocation
942 described above. For a path that is added, removed, or modified,
943 `GIT_EXTERNAL_DIFF` is called with 7 parameters:
945 path old-file old-hex old-mode new-file new-hex new-mode
949 <old|new>-file:: are files GIT_EXTERNAL_DIFF can use to read the
950 contents of <old|new>,
951 <old|new>-hex:: are the 40-hexdigit SHA-1 hashes,
952 <old|new>-mode:: are the octal representation of the file modes.
954 The file parameters can point at the user's working file
955 (e.g. `new-file` in "git-diff-files"), `/dev/null` (e.g. `old-file`
956 when a new file is added), or a temporary file (e.g. `old-file` in the
957 index). `GIT_EXTERNAL_DIFF` should not worry about unlinking the
958 temporary file --- it is removed when `GIT_EXTERNAL_DIFF` exits.
960 For a path that is unmerged, `GIT_EXTERNAL_DIFF` is called with 1
963 For each path `GIT_EXTERNAL_DIFF` is called, two environment variables,
964 `GIT_DIFF_PATH_COUNTER` and `GIT_DIFF_PATH_TOTAL` are set.
966 `GIT_DIFF_PATH_COUNTER`::
967 A 1-based counter incremented by one for every path.
969 `GIT_DIFF_PATH_TOTAL`::
970 The total number of paths.
974 `GIT_MERGE_VERBOSITY`::
975 A number controlling the amount of output shown by
976 the recursive merge strategy. Overrides merge.verbosity.
977 See linkgit:git-merge[1]
980 This environment variable overrides `$PAGER`. If it is set
981 to an empty string or to the value "cat", Git will not launch
982 a pager. See also the `core.pager` option in
983 linkgit:git-config[1].
986 This environment variable overrides `$EDITOR` and `$VISUAL`.
987 It is used by several Git commands when, on interactive mode,
988 an editor is to be launched. See also linkgit:git-var[1]
989 and the `core.editor` option in linkgit:git-config[1].
993 If either of these environment variables is set then 'git fetch'
994 and 'git push' will use the specified command instead of 'ssh'
995 when they need to connect to a remote system.
996 The command will be given exactly two or four arguments: the
997 'username@host' (or just 'host') from the URL and the shell
998 command to execute on that remote system, optionally preceded by
999 `-p` (literally) and the 'port' from the URL when it specifies
1000 something other than the default SSH port.
1002 `$GIT_SSH_COMMAND` takes precedence over `$GIT_SSH`, and is interpreted
1003 by the shell, which allows additional arguments to be included.
1004 `$GIT_SSH` on the other hand must be just the path to a program
1005 (which can be a wrapper shell script, if additional arguments are
1008 Usually it is easier to configure any desired options through your
1009 personal `.ssh/config` file. Please consult your ssh documentation
1010 for further details.
1013 If this environment variable is set, then Git commands which need to
1014 acquire passwords or passphrases (e.g. for HTTP or IMAP authentication)
1015 will call this program with a suitable prompt as command-line argument
1016 and read the password from its STDOUT. See also the `core.askPass`
1017 option in linkgit:git-config[1].
1019 `GIT_TERMINAL_PROMPT`::
1020 If this environment variable is set to `0`, git will not prompt
1021 on the terminal (e.g., when asking for HTTP authentication).
1023 `GIT_CONFIG_NOSYSTEM`::
1024 Whether to skip reading settings from the system-wide
1025 `$(prefix)/etc/gitconfig` file. This environment variable can
1026 be used along with `$HOME` and `$XDG_CONFIG_HOME` to create a
1027 predictable environment for a picky script, or you can set it
1028 temporarily to avoid using a buggy `/etc/gitconfig` file while
1029 waiting for someone with sufficient permissions to fix it.
1032 If this environment variable is set to "1", then commands such
1033 as 'git blame' (in incremental mode), 'git rev-list', 'git log',
1034 'git check-attr' and 'git check-ignore' will
1035 force a flush of the output stream after each record have been
1037 variable is set to "0", the output of these commands will be done
1038 using completely buffered I/O. If this environment variable is
1039 not set, Git will choose buffered or record-oriented flushing
1040 based on whether stdout appears to be redirected to a file or not.
1043 Enables general trace messages, e.g. alias expansion, built-in
1044 command execution and external command execution.
1046 If this variable is set to "1", "2" or "true" (comparison
1047 is case insensitive), trace messages will be printed to
1050 If the variable is set to an integer value greater than 2
1051 and lower than 10 (strictly) then Git will interpret this
1052 value as an open file descriptor and will try to write the
1053 trace messages into this file descriptor.
1055 Alternatively, if the variable is set to an absolute path
1056 (starting with a '/' character), Git will interpret this
1057 as a file path and will try to write the trace messages
1060 Unsetting the variable, or setting it to empty, "0" or
1061 "false" (case insensitive) disables trace messages.
1063 `GIT_TRACE_PACK_ACCESS`::
1064 Enables trace messages for all accesses to any packs. For each
1065 access, the pack file name and an offset in the pack is
1066 recorded. This may be helpful for troubleshooting some
1067 pack-related performance problems.
1068 See `GIT_TRACE` for available trace output options.
1070 `GIT_TRACE_PACKET`::
1071 Enables trace messages for all packets coming in or out of a
1072 given program. This can help with debugging object negotiation
1073 or other protocol issues. Tracing is turned off at a packet
1074 starting with "PACK" (but see `GIT_TRACE_PACKFILE` below).
1075 See `GIT_TRACE` for available trace output options.
1077 `GIT_TRACE_PACKFILE`::
1078 Enables tracing of packfiles sent or received by a
1079 given program. Unlike other trace output, this trace is
1080 verbatim: no headers, and no quoting of binary data. You almost
1081 certainly want to direct into a file (e.g.,
1082 `GIT_TRACE_PACKFILE=/tmp/my.pack`) rather than displaying it on
1083 the terminal or mixing it with other trace output.
1085 Note that this is currently only implemented for the client side
1086 of clones and fetches.
1088 `GIT_TRACE_PERFORMANCE`::
1089 Enables performance related trace messages, e.g. total execution
1090 time of each Git command.
1091 See `GIT_TRACE` for available trace output options.
1094 Enables trace messages printing the .git, working tree and current
1095 working directory after Git has completed its setup phase.
1096 See `GIT_TRACE` for available trace output options.
1098 `GIT_TRACE_SHALLOW`::
1099 Enables trace messages that can help debugging fetching /
1100 cloning of shallow repositories.
1101 See `GIT_TRACE` for available trace output options.
1104 Enables a curl full trace dump of all incoming and outgoing data,
1105 including descriptive information, of the git transport protocol.
1106 This is similar to doing curl `--trace-ascii` on the command line.
1107 This option overrides setting the `GIT_CURL_VERBOSE` environment
1109 See `GIT_TRACE` for available trace output options.
1111 `GIT_LITERAL_PATHSPECS`::
1112 Setting this variable to `1` will cause Git to treat all
1113 pathspecs literally, rather than as glob patterns. For example,
1114 running `GIT_LITERAL_PATHSPECS=1 git log -- '*.c'` will search
1115 for commits that touch the path `*.c`, not any paths that the
1116 glob `*.c` matches. You might want this if you are feeding
1117 literal paths to Git (e.g., paths previously given to you by
1118 `git ls-tree`, `--raw` diff output, etc).
1120 `GIT_GLOB_PATHSPECS`::
1121 Setting this variable to `1` will cause Git to treat all
1122 pathspecs as glob patterns (aka "glob" magic).
1124 `GIT_NOGLOB_PATHSPECS`::
1125 Setting this variable to `1` will cause Git to treat all
1126 pathspecs as literal (aka "literal" magic).
1128 `GIT_ICASE_PATHSPECS`::
1129 Setting this variable to `1` will cause Git to treat all
1130 pathspecs as case-insensitive.
1132 `GIT_REFLOG_ACTION`::
1133 When a ref is updated, reflog entries are created to keep
1134 track of the reason why the ref was updated (which is
1135 typically the name of the high-level command that updated
1136 the ref), in addition to the old and new values of the ref.
1137 A scripted Porcelain command can use set_reflog_action
1138 helper function in `git-sh-setup` to set its name to this
1139 variable when it is invoked as the top level command by the
1140 end user, to be recorded in the body of the reflog.
1142 `GIT_REF_PARANOIA`::
1143 If set to `1`, include broken or badly named refs when iterating
1144 over lists of refs. In a normal, non-corrupted repository, this
1145 does nothing. However, enabling it may help git to detect and
1146 abort some operations in the presence of broken refs. Git sets
1147 this variable automatically when performing destructive
1148 operations like linkgit:git-prune[1]. You should not need to set
1149 it yourself unless you want to be paranoid about making sure
1150 an operation has touched every ref (e.g., because you are
1151 cloning a repository to make a backup).
1153 `GIT_ALLOW_PROTOCOL`::
1154 If set, provide a colon-separated list of protocols which are
1155 allowed to be used with fetch/push/clone. This is useful to
1156 restrict recursive submodule initialization from an untrusted
1157 repository. Any protocol not mentioned will be disallowed (i.e.,
1158 this is a whitelist, not a blacklist). If the variable is not
1159 set at all, all protocols are enabled. The protocol names
1160 currently used by git are:
1162 - `file`: any local file-based path (including `file://` URLs,
1165 - `git`: the anonymous git protocol over a direct TCP
1166 connection (or proxy, if configured)
1168 - `ssh`: git over ssh (including `host:path` syntax,
1171 - `http`: git over http, both "smart http" and "dumb http".
1172 Note that this does _not_ include `https`; if you want both,
1173 you should specify both as `http:https`.
1175 - any external helpers are named by their protocol (e.g., use
1176 `hg` to allow the `git-remote-hg` helper)
1179 Discussion[[Discussion]]
1180 ------------------------
1182 More detail on the following is available from the
1183 link:user-manual.html#git-concepts[Git concepts chapter of the
1184 user-manual] and linkgit:gitcore-tutorial[7].
1186 A Git project normally consists of a working directory with a ".git"
1187 subdirectory at the top level. The .git directory contains, among other
1188 things, a compressed object database representing the complete history
1189 of the project, an "index" file which links that history to the current
1190 contents of the working tree, and named pointers into that history such
1191 as tags and branch heads.
1193 The object database contains objects of three main types: blobs, which
1194 hold file data; trees, which point to blobs and other trees to build up
1195 directory hierarchies; and commits, which each reference a single tree
1196 and some number of parent commits.
1198 The commit, equivalent to what other systems call a "changeset" or
1199 "version", represents a step in the project's history, and each parent
1200 represents an immediately preceding step. Commits with more than one
1201 parent represent merges of independent lines of development.
1203 All objects are named by the SHA-1 hash of their contents, normally
1204 written as a string of 40 hex digits. Such names are globally unique.
1205 The entire history leading up to a commit can be vouched for by signing
1206 just that commit. A fourth object type, the tag, is provided for this
1209 When first created, objects are stored in individual files, but for
1210 efficiency may later be compressed together into "pack files".
1212 Named pointers called refs mark interesting points in history. A ref
1213 may contain the SHA-1 name of an object or the name of another ref. Refs
1214 with names beginning `ref/head/` contain the SHA-1 name of the most
1215 recent commit (or "head") of a branch under development. SHA-1 names of
1216 tags of interest are stored under `ref/tags/`. A special ref named
1217 `HEAD` contains the name of the currently checked-out branch.
1219 The index file is initialized with a list of all paths and, for each
1220 path, a blob object and a set of attributes. The blob object represents
1221 the contents of the file as of the head of the current branch. The
1222 attributes (last modified time, size, etc.) are taken from the
1223 corresponding file in the working tree. Subsequent changes to the
1224 working tree can be found by comparing these attributes. The index may
1225 be updated with new content, and new commits may be created from the
1226 content stored in the index.
1228 The index is also capable of storing multiple entries (called "stages")
1229 for a given pathname. These stages are used to hold the various
1230 unmerged version of a file when a merge is in progress.
1232 FURTHER DOCUMENTATION
1233 ---------------------
1235 See the references in the "description" section to get started
1236 using Git. The following is probably more detail than necessary
1237 for a first-time user.
1239 The link:user-manual.html#git-concepts[Git concepts chapter of the
1240 user-manual] and linkgit:gitcore-tutorial[7] both provide
1241 introductions to the underlying Git architecture.
1243 See linkgit:gitworkflows[7] for an overview of recommended workflows.
1245 See also the link:howto-index.html[howto] documents for some useful
1248 The internals are documented in the
1249 link:technical/api-index.html[Git API documentation].
1251 Users migrating from CVS may also want to
1252 read linkgit:gitcvs-migration[7].
1257 Git was started by Linus Torvalds, and is currently maintained by Junio
1258 C Hamano. Numerous contributions have come from the Git mailing list
1259 <git@vger.kernel.org>. http://www.openhub.net/p/git/contributors/summary
1260 gives you a more complete list of contributors.
1262 If you have a clone of git.git itself, the
1263 output of linkgit:git-shortlog[1] and linkgit:git-blame[1] can show you
1264 the authors for specific parts of the project.
1269 Report bugs to the Git mailing list <git@vger.kernel.org> where the
1270 development and maintenance is primarily done. You do not have to be
1271 subscribed to the list to send a message there.
1275 linkgit:gittutorial[7], linkgit:gittutorial-2[7],
1276 linkgit:giteveryday[7], linkgit:gitcvs-migration[7],
1277 linkgit:gitglossary[7], linkgit:gitcore-tutorial[7],
1278 linkgit:gitcli[7], link:user-manual.html[The Git User's Manual],
1279 linkgit:gitworkflows[7]
1283 Part of the linkgit:git[1] suite