]>
Commit | Line | Data |
---|---|---|
df0b6cfb NTND |
1 | git-worktree(1) |
2 | =============== | |
3 | ||
4 | NAME | |
5 | ---- | |
bc483285 | 6 | git-worktree - Manage multiple working trees |
df0b6cfb NTND |
7 | |
8 | ||
9 | SYNOPSIS | |
10 | -------- | |
11 | [verse] | |
0db4961c | 12 | 'git worktree add' [-f] [--detach] [--checkout] [--lock [--reason <string>]] [-b <new-branch>] <path> [<commit-ish>] |
bb9c03b8 | 13 | 'git worktree list' [--porcelain] |
58142c09 | 14 | 'git worktree lock' [--reason <string>] <worktree> |
9f792bb4 | 15 | 'git worktree move' <worktree> <new-path> |
7b722d90 | 16 | 'git worktree prune' [-n] [-v] [--expire <expire>] |
d228eea5 | 17 | 'git worktree remove' [-f] <worktree> |
b214ab5a | 18 | 'git worktree repair' [<path>...] |
6d308627 | 19 | 'git worktree unlock' <worktree> |
df0b6cfb NTND |
20 | |
21 | DESCRIPTION | |
22 | ----------- | |
23 | ||
bc483285 | 24 | Manage multiple working trees attached to the same repository. |
df0b6cfb | 25 | |
93a36493 | 26 | A git repository can support multiple working trees, allowing you to check |
4d5a3c58 | 27 | out more than one branch at a time. With `git worktree add` a new working |
93a36493 | 28 | tree is associated with the repository. This new working tree is called a |
dc9c144b ES |
29 | "linked working tree" as opposed to the "main working tree" prepared by |
30 | linkgit:git-init[1] or linkgit:git-clone[1]. | |
31 | A repository has one main working tree (if it's not a | |
3f0b42bd ES |
32 | bare repository) and zero or more linked working trees. When you are done |
33 | with a linked working tree, remove it with `git worktree remove`. | |
93a36493 | 34 | |
dccadad7 ES |
35 | In its simplest form, `git worktree add <path>` automatically creates a |
36 | new branch whose name is the final component of `<path>`, which is | |
37 | convenient if you plan to work on a new topic. For instance, `git | |
38 | worktree add ../hotfix` creates new branch `hotfix` and checks it out at | |
39 | path `../hotfix`. To instead work on an existing branch in a new working | |
40 | tree, use `git worktree add <path> <branch>`. On the other hand, if you | |
41 | just plan to make some experimental changes or do testing without | |
42 | disturbing existing development, it is often convenient to create a | |
43 | 'throwaway' working tree not associated with any branch. For instance, | |
44 | `git worktree add -d <path>` creates a new working tree with a detached | |
45 | `HEAD` at the same commit as the current branch. | |
46 | ||
3f0b42bd ES |
47 | If a working tree is deleted without using `git worktree remove`, then |
48 | its associated administrative files, which reside in the repository | |
49 | (see "DETAILS" below), will eventually be removed automatically (see | |
5f5f553f | 50 | `gc.worktreePruneExpire` in linkgit:git-config[1]), or you can run |
93a36493 | 51 | `git worktree prune` in the main or any linked working tree to |
af189b4c | 52 | clean up any stale administrative files. |
93a36493 | 53 | |
a8ba5dd7 ES |
54 | If a linked working tree is stored on a portable device or network share |
55 | which is not always mounted, you can prevent its administrative files from | |
58142c09 NTND |
56 | being pruned by issuing the `git worktree lock` command, optionally |
57 | specifying `--reason` to explain why the working tree is locked. | |
93a36493 | 58 | |
df0b6cfb NTND |
59 | COMMANDS |
60 | -------- | |
c4738aed | 61 | add <path> [<commit-ish>]:: |
fc56361f | 62 | |
c4738aed | 63 | Create `<path>` and checkout `<commit-ish>` into it. The new working directory |
fc56361f | 64 | is linked to the current repository, sharing everything except working |
1933f6ce ES |
65 | directory specific files such as `HEAD`, `index`, etc. As a convenience, |
66 | `<commit-ish>` may be a bare "`-`", which is synonymous with `@{-1}`. | |
1eb07d82 | 67 | + |
e79e313c | 68 | If `<commit-ish>` is a branch name (call it `<branch>`) and is not found, |
4e853331 TG |
69 | and neither `-b` nor `-B` nor `--detach` are used, but there does |
70 | exist a tracking branch in exactly one remote (call it `<remote>`) | |
661a5a38 | 71 | with a matching name, treat as equivalent to: |
d023df1e | 72 | + |
4e853331 TG |
73 | ------------ |
74 | $ git worktree add --track -b <branch> <path> <remote>/<branch> | |
75 | ------------ | |
76 | + | |
8d7b558b ÆAB |
77 | If the branch exists in multiple remotes and one of them is named by |
78 | the `checkout.defaultRemote` configuration variable, we'll use that | |
79 | one for the purposes of disambiguation, even if the `<branch>` isn't | |
80 | unique across all remotes. Set it to | |
81 | e.g. `checkout.defaultRemote=origin` to always checkout remote | |
82 | branches from there if `<branch>` is ambiguous but exists on the | |
e79e313c | 83 | `origin` remote. See also `checkout.defaultRemote` in |
8d7b558b ÆAB |
84 | linkgit:git-config[1]. |
85 | + | |
c4738aed | 86 | If `<commit-ish>` is omitted and neither `-b` nor `-B` nor `--detach` used, |
4f375b26 | 87 | then, as a convenience, the new working tree is associated with a branch |
f60a7b76 | 88 | (call it `<branch>`) named after `$(basename <path>)`. If `<branch>` |
e79e313c | 89 | doesn't exist, a new branch based on `HEAD` is automatically created as |
f60a7b76 | 90 | if `-b <branch>` was given. If `<branch>` does exist, it will be |
4f375b26 ES |
91 | checked out in the new working tree, if it's not checked out anywhere |
92 | else, otherwise the command will refuse to create the working tree (unless | |
f60a7b76 | 93 | `--force` is used). |
fc56361f | 94 | |
bb9c03b8 MR |
95 | list:: |
96 | ||
4f375b26 ES |
97 | List details of each working tree. The main working tree is listed first, |
98 | followed by each of the linked working trees. The output details include | |
c57b3367 | 99 | whether the working tree is bare, the revision currently checked out, the |
9b19a58f RS |
100 | branch currently checked out (or "detached HEAD" if none), "locked" if |
101 | the worktree is locked, "prunable" if the worktree can be pruned by `prune` | |
102 | command. | |
bb9c03b8 | 103 | |
58142c09 NTND |
104 | lock:: |
105 | ||
106 | If a working tree is on a portable device or network share which | |
107 | is not always mounted, lock it to prevent its administrative | |
108 | files from being pruned automatically. This also prevents it from | |
109 | being moved or deleted. Optionally, specify a reason for the lock | |
110 | with `--reason`. | |
111 | ||
9f792bb4 NTND |
112 | move:: |
113 | ||
114 | Move a working tree to a new location. Note that the main working tree | |
bdd1f3e4 ES |
115 | or linked working trees containing submodules cannot be moved with this |
116 | command. (The `git worktree repair` command, however, can reestablish | |
117 | the connection with linked working trees if you move the main working | |
118 | tree manually.) | |
9f792bb4 | 119 | |
7b722d90 NTND |
120 | prune:: |
121 | ||
e79e313c | 122 | Prune working tree information in `$GIT_DIR/worktrees`. |
7b722d90 | 123 | |
cc73385c NTND |
124 | remove:: |
125 | ||
126 | Remove a working tree. Only clean working trees (no untracked files | |
127 | and no modification in tracked files) can be removed. Unclean working | |
128 | trees or ones with submodules can be removed with `--force`. The main | |
129 | working tree cannot be removed. | |
130 | ||
b214ab5a | 131 | repair [<path>...]:: |
e8e1ff24 ES |
132 | |
133 | Repair working tree administrative files, if possible, if they have | |
134 | become corrupted or outdated due to external factors. | |
bdd1f3e4 ES |
135 | + |
136 | For instance, if the main working tree (or bare repository) is moved, | |
137 | linked working trees will be unable to locate it. Running `repair` in | |
138 | the main working tree will reestablish the connection from linked | |
139 | working trees back to the main working tree. | |
b214ab5a ES |
140 | + |
141 | Similarly, if a linked working tree is moved without using `git worktree | |
142 | move`, the main working tree (or bare repository) will be unable to | |
143 | locate it. Running `repair` within the recently-moved working tree will | |
144 | reestablish the connection. If multiple linked working trees are moved, | |
145 | running `repair` from any working tree with each tree's new `<path>` as | |
146 | an argument, will reestablish the connection to all the specified paths. | |
cf76baea ES |
147 | + |
148 | If both the main working tree and linked working trees have been moved | |
149 | manually, then running `repair` in the main working tree and specifying the | |
150 | new `<path>` of each linked working tree will reestablish all connections | |
151 | in both directions. | |
e8e1ff24 | 152 | |
6d308627 NTND |
153 | unlock:: |
154 | ||
155 | Unlock a working tree, allowing it to be pruned, moved or deleted. | |
156 | ||
df0b6cfb NTND |
157 | OPTIONS |
158 | ------- | |
159 | ||
f4325444 ES |
160 | -f:: |
161 | --force:: | |
cc73385c NTND |
162 | By default, `add` refuses to create a new working tree when |
163 | `<commit-ish>` is a branch name and is already checked out by | |
e19831c9 ES |
164 | another working tree, or if `<path>` is already assigned to some |
165 | working tree but is missing (for instance, if `<path>` was deleted | |
166 | manually). This option overrides these safeguards. To add a missing but | |
167 | locked working tree path, specify `--force` twice. | |
168 | + | |
68a6b3a1 | 169 | `move` refuses to move a locked working tree unless `--force` is specified |
810382ed ES |
170 | twice. If the destination is already assigned to some other working tree but is |
171 | missing (for instance, if `<new-path>` was deleted manually), then `--force` | |
e79e313c | 172 | allows the move to proceed; use `--force` twice if the destination is locked. |
68a6b3a1 | 173 | + |
e19831c9 | 174 | `remove` refuses to remove an unclean working tree unless `--force` is used. |
f4143101 | 175 | To remove a locked working tree, specify `--force` twice. |
f4325444 | 176 | |
cbdf60fa ES |
177 | -b <new-branch>:: |
178 | -B <new-branch>:: | |
179 | With `add`, create a new branch named `<new-branch>` starting at | |
c4738aed | 180 | `<commit-ish>`, and check out `<new-branch>` into the new working tree. |
e79e313c | 181 | If `<commit-ish>` is omitted, it defaults to `HEAD`. |
cbdf60fa ES |
182 | By default, `-b` refuses to create a new branch if it already |
183 | exists. `-B` overrides this safeguard, resetting `<new-branch>` to | |
c4738aed | 184 | `<commit-ish>`. |
cbdf60fa | 185 | |
c670aa47 | 186 | -d:: |
39ecb274 | 187 | --detach:: |
e79e313c | 188 | With `add`, detach `HEAD` in the new working tree. See "DETACHED HEAD" |
bc483285 | 189 | in linkgit:git-checkout[1]. |
39ecb274 | 190 | |
ef2a0ac9 | 191 | --[no-]checkout:: |
c4738aed | 192 | By default, `add` checks out `<commit-ish>`, however, `--no-checkout` can |
ef2a0ac9 RZ |
193 | be used to suppress checkout in order to make customizations, |
194 | such as configuring sparse-checkout. See "Sparse checkout" | |
195 | in linkgit:git-read-tree[1]. | |
196 | ||
71d6682d TG |
197 | --[no-]guess-remote:: |
198 | With `worktree add <path>`, without `<commit-ish>`, instead | |
e79e313c | 199 | of creating a new branch from `HEAD`, if there exists a tracking |
50fdf7b1 | 200 | branch in exactly one remote matching the basename of `<path>`, |
71d6682d TG |
201 | base the new branch on the remote-tracking branch, and mark |
202 | the remote-tracking branch as "upstream" from the new branch. | |
e92445a7 TG |
203 | + |
204 | This can also be set up as the default behaviour by using the | |
205 | `worktree.guessRemote` config option. | |
71d6682d | 206 | |
e284e892 TG |
207 | --[no-]track:: |
208 | When creating a new branch, if `<commit-ish>` is a branch, | |
209 | mark it as "upstream" from the new branch. This is the | |
210 | default if `<commit-ish>` is a remote-tracking branch. See | |
e79e313c | 211 | `--track` in linkgit:git-branch[1] for details. |
e284e892 | 212 | |
507e6e9e NTND |
213 | --lock:: |
214 | Keep the working tree locked after creation. This is the | |
215 | equivalent of `git worktree lock` after `git worktree add`, | |
ff1ce500 | 216 | but without a race condition. |
507e6e9e | 217 | |
df0b6cfb NTND |
218 | -n:: |
219 | --dry-run:: | |
4f09825e | 220 | With `prune`, do not remove anything; just report what it would |
df0b6cfb NTND |
221 | remove. |
222 | ||
bb9c03b8 MR |
223 | --porcelain:: |
224 | With `list`, output in an easy-to-parse format for scripts. | |
225 | This format will remain stable across Git versions and regardless of user | |
226 | configuration. See below for details. | |
227 | ||
371979c2 EP |
228 | -q:: |
229 | --quiet:: | |
e79e313c | 230 | With `add`, suppress feedback messages. |
371979c2 | 231 | |
df0b6cfb NTND |
232 | -v:: |
233 | --verbose:: | |
4f09825e | 234 | With `prune`, report all removals. |
076b444a RS |
235 | + |
236 | With `list`, output additional information about worktrees (see below). | |
df0b6cfb NTND |
237 | |
238 | --expire <time>:: | |
e79e313c | 239 | With `prune`, only expire unused working trees older than `<time>`. |
9b19a58f RS |
240 | + |
241 | With `list`, annotate missing working trees as prunable if they are | |
242 | older than `<time>`. | |
df0b6cfb | 243 | |
58142c09 | 244 | --reason <string>:: |
0db4961c | 245 | With `lock` or with `add --lock`, an explanation why the working tree is locked. |
58142c09 NTND |
246 | |
247 | <worktree>:: | |
248 | Working trees can be identified by path, either relative or | |
249 | absolute. | |
080739ba NTND |
250 | + |
251 | If the last path components in the working tree's path is unique among | |
ff1ce500 | 252 | working trees, it can be used to identify a working tree. For example if |
e79e313c ES |
253 | you only have two working trees, at `/abc/def/ghi` and `/abc/def/ggg`, |
254 | then `ghi` or `def/ghi` is enough to point to the former working tree. | |
58142c09 | 255 | |
8aff1a9c NTND |
256 | REFS |
257 | ---- | |
258 | In multiple working trees, some refs may be shared between all working | |
ff1ce500 ES |
259 | trees and some refs are local. One example is `HEAD` which is different for each |
260 | working tree. This section is about the sharing rules and how to access | |
3a3b9d8c | 261 | refs of one working tree from another. |
8aff1a9c NTND |
262 | |
263 | In general, all pseudo refs are per working tree and all refs starting | |
e79e313c | 264 | with `refs/` are shared. Pseudo refs are ones like `HEAD` which are |
ff1ce500 ES |
265 | directly under `$GIT_DIR` instead of inside `$GIT_DIR/refs`. There are |
266 | exceptions, however: refs inside `refs/bisect` and `refs/worktree` are not | |
8aff1a9c NTND |
267 | shared. |
268 | ||
3a3b9d8c | 269 | Refs that are per working tree can still be accessed from another |
e79e313c | 270 | working tree via two special paths, `main-worktree` and `worktrees`. The |
4f375b26 | 271 | former gives access to per-working tree refs of the main working tree, |
3a3b9d8c NTND |
272 | while the latter to all linked working trees. |
273 | ||
e79e313c ES |
274 | For example, `main-worktree/HEAD` or `main-worktree/refs/bisect/good` |
275 | resolve to the same value as the main working tree's `HEAD` and | |
276 | `refs/bisect/good` respectively. Similarly, `worktrees/foo/HEAD` or | |
277 | `worktrees/bar/refs/bisect/bad` are the same as | |
278 | `$GIT_COMMON_DIR/worktrees/foo/HEAD` and | |
279 | `$GIT_COMMON_DIR/worktrees/bar/refs/bisect/bad`. | |
3a3b9d8c | 280 | |
e79e313c | 281 | To access refs, it's best not to look inside `$GIT_DIR` directly. Instead |
14f74d59 | 282 | use commands such as linkgit:git-rev-parse[1] or linkgit:git-update-ref[1] |
8aff1a9c NTND |
283 | which will handle refs correctly. |
284 | ||
58b284a2 NTND |
285 | CONFIGURATION FILE |
286 | ------------------ | |
e79e313c | 287 | By default, the repository `config` file is shared across all working |
58b284a2 NTND |
288 | trees. If the config variables `core.bare` or `core.worktree` are |
289 | already present in the config file, they will be applied to the main | |
290 | working trees only. | |
291 | ||
292 | In order to have configuration specific to working trees, you can turn | |
ff1ce500 | 293 | on the `worktreeConfig` extension, e.g.: |
58b284a2 NTND |
294 | |
295 | ------------ | |
296 | $ git config extensions.worktreeConfig true | |
297 | ------------ | |
298 | ||
299 | In this mode, specific configuration stays in the path pointed by `git | |
300 | rev-parse --git-path config.worktree`. You can add or update | |
301 | configuration in this file with `git config --worktree`. Older Git | |
302 | versions will refuse to access repositories with this extension. | |
303 | ||
304 | Note that in this file, the exception for `core.bare` and `core.worktree` | |
ff1ce500 | 305 | is gone. If they exist in `$GIT_DIR/config`, you must move |
58b284a2 NTND |
306 | them to the `config.worktree` of the main working tree. You may also |
307 | take this opportunity to review and move other configuration that you | |
308 | do not want to share to all working trees: | |
309 | ||
310 | - `core.worktree` and `core.bare` should never be shared | |
311 | ||
312 | - `core.sparseCheckout` is recommended per working tree, unless you | |
313 | are sure you always use sparse checkout for all working trees. | |
314 | ||
af189b4c ES |
315 | DETAILS |
316 | ------- | |
317 | Each linked working tree has a private sub-directory in the repository's | |
e79e313c | 318 | `$GIT_DIR/worktrees` directory. The private sub-directory's name is usually |
af189b4c ES |
319 | the base name of the linked working tree's path, possibly appended with a |
320 | number to make it unique. For example, when `$GIT_DIR=/path/main/.git` the | |
4d5a3c58 | 321 | command `git worktree add /path/other/test-next next` creates the linked |
af189b4c ES |
322 | working tree in `/path/other/test-next` and also creates a |
323 | `$GIT_DIR/worktrees/test-next` directory (or `$GIT_DIR/worktrees/test-next1` | |
324 | if `test-next` is already taken). | |
325 | ||
e79e313c | 326 | Within a linked working tree, `$GIT_DIR` is set to point to this private |
af189b4c | 327 | directory (e.g. `/path/main/.git/worktrees/test-next` in the example) and |
e79e313c | 328 | `$GIT_COMMON_DIR` is set to point back to the main working tree's `$GIT_DIR` |
af189b4c ES |
329 | (e.g. `/path/main/.git`). These settings are made in a `.git` file located at |
330 | the top directory of the linked working tree. | |
331 | ||
332 | Path resolution via `git rev-parse --git-path` uses either | |
e79e313c | 333 | `$GIT_DIR` or `$GIT_COMMON_DIR` depending on the path. For example, in the |
af189b4c ES |
334 | linked working tree `git rev-parse --git-path HEAD` returns |
335 | `/path/main/.git/worktrees/test-next/HEAD` (not | |
336 | `/path/other/test-next/.git/HEAD` or `/path/main/.git/HEAD`) while `git | |
337 | rev-parse --git-path refs/heads/master` uses | |
e79e313c ES |
338 | `$GIT_COMMON_DIR` and returns `/path/main/.git/refs/heads/master`, |
339 | since refs are shared across all working trees, except `refs/bisect` and | |
340 | `refs/worktree`. | |
af189b4c ES |
341 | |
342 | See linkgit:gitrepository-layout[5] for more information. The rule of | |
343 | thumb is do not make any assumption about whether a path belongs to | |
e79e313c ES |
344 | `$GIT_DIR` or `$GIT_COMMON_DIR` when you need to directly access something |
345 | inside `$GIT_DIR`. Use `git rev-parse --git-path` to get the final path. | |
af189b4c | 346 | |
e79e313c | 347 | If you manually move a linked working tree, you need to update the `gitdir` file |
618244e1 NTND |
348 | in the entry's directory. For example, if a linked working tree is moved |
349 | to `/newpath/test-next` and its `.git` file points to | |
350 | `/path/main/.git/worktrees/test-next`, then update | |
351 | `/path/main/.git/worktrees/test-next/gitdir` to reference `/newpath/test-next` | |
b214ab5a ES |
352 | instead. Better yet, run `git worktree repair` to reestablish the connection |
353 | automatically. | |
618244e1 | 354 | |
e79e313c | 355 | To prevent a `$GIT_DIR/worktrees` entry from being pruned (which |
a8ba5dd7 | 356 | can be useful in some situations, such as when the |
58142c09 NTND |
357 | entry's working tree is stored on a portable device), use the |
358 | `git worktree lock` command, which adds a file named | |
e79e313c | 359 | `locked` to the entry's directory. The file contains the reason in |
a8ba5dd7 ES |
360 | plain text. For example, if a linked working tree's `.git` file points |
361 | to `/path/main/.git/worktrees/test-next` then a file named | |
362 | `/path/main/.git/worktrees/test-next/locked` will prevent the | |
363 | `test-next` entry from being pruned. See | |
364 | linkgit:gitrepository-layout[5] for details. | |
365 | ||
e79e313c | 366 | When `extensions.worktreeConfig` is enabled, the config file |
58b284a2 | 367 | `.git/worktrees/<id>/config.worktree` is read after `.git/config` is. |
a8ba5dd7 | 368 | |
bb9c03b8 MR |
369 | LIST OUTPUT FORMAT |
370 | ------------------ | |
e79e313c | 371 | The `worktree list` command has two output formats. The default format shows the |
bb9c03b8 MR |
372 | details on a single line with columns. For example: |
373 | ||
374 | ------------ | |
22d11a6e | 375 | $ git worktree list |
bb9c03b8 MR |
376 | /path/to/bare-source (bare) |
377 | /path/to/linked-worktree abcd1234 [master] | |
378 | /path/to/other-linked-worktree 1234abc (detached HEAD) | |
379 | ------------ | |
380 | ||
9b19a58f RS |
381 | The command also shows annotations for each working tree, according to its state. |
382 | These annotations are: | |
383 | ||
384 | * `locked`, if the working tree is locked. | |
385 | * `prunable`, if the working tree can be pruned via `git worktree prune`. | |
386 | ||
387 | ------------ | |
388 | $ git worktree list | |
389 | /path/to/linked-worktree abcd1234 [master] | |
98c7656a | 390 | /path/to/locked-worktree acbd5678 (brancha) locked |
9b19a58f RS |
391 | /path/to/prunable-worktree 5678abc (detached HEAD) prunable |
392 | ------------ | |
393 | ||
076b444a RS |
394 | For these annotations, a reason might also be available and this can be |
395 | seen using the verbose mode. The annotation is then moved to the next line | |
396 | indented followed by the additional information. | |
397 | ||
398 | ------------ | |
399 | $ git worktree list --verbose | |
400 | /path/to/linked-worktree abcd1234 [master] | |
401 | /path/to/locked-worktree-no-reason abcd5678 (detached HEAD) locked | |
402 | /path/to/locked-worktree-with-reason 1234abcd (brancha) | |
403 | locked: working tree path is mounted on a portable device | |
404 | /path/to/prunable-worktree 5678abc1 (detached HEAD) | |
405 | prunable: gitdir file points to non-existent location | |
406 | ------------ | |
407 | ||
408 | Note that the annotation is moved to the next line if the additional | |
409 | information is available, otherwise it stays on the same line as the | |
410 | working tree itself. | |
411 | ||
bb9c03b8 MR |
412 | Porcelain Format |
413 | ~~~~~~~~~~~~~~~~ | |
414 | The porcelain format has a line per attribute. Attributes are listed with a | |
e79e313c | 415 | label and value separated by a single space. Boolean attributes (like `bare` |
ff1ce500 | 416 | and `detached`) are listed as a label only, and are present only |
862c723d RS |
417 | if the value is true. Some attributes (like `locked`) can be listed as a label |
418 | only or with a value depending upon whether a reason is available. The first | |
419 | attribute of a working tree is always `worktree`, an empty line indicates the | |
420 | end of the record. For example: | |
bb9c03b8 MR |
421 | |
422 | ------------ | |
22d11a6e | 423 | $ git worktree list --porcelain |
bb9c03b8 MR |
424 | worktree /path/to/bare-source |
425 | bare | |
426 | ||
427 | worktree /path/to/linked-worktree | |
428 | HEAD abcd1234abcd1234abcd1234abcd1234abcd1234 | |
429 | branch refs/heads/master | |
430 | ||
431 | worktree /path/to/other-linked-worktree | |
432 | HEAD 1234abc1234abc1234abc1234abc1234abc1234a | |
433 | detached | |
434 | ||
862c723d RS |
435 | worktree /path/to/linked-worktree-locked-no-reason |
436 | HEAD 5678abc5678abc5678abc5678abc5678abc5678c | |
437 | branch refs/heads/locked-no-reason | |
438 | locked | |
439 | ||
440 | worktree /path/to/linked-worktree-locked-with-reason | |
441 | HEAD 3456def3456def3456def3456def3456def3456b | |
442 | branch refs/heads/locked-with-reason | |
443 | locked reason why is locked | |
444 | ||
9b19a58f RS |
445 | worktree /path/to/linked-worktree-prunable |
446 | HEAD 1233def1234def1234def1234def1234def1234b | |
447 | detached | |
448 | prunable gitdir file points to non-existent location | |
449 | ||
862c723d RS |
450 | ------------ |
451 | ||
452 | If the lock reason contains "unusual" characters such as newline, they | |
453 | are escaped and the entire reason is quoted as explained for the | |
454 | configuration variable `core.quotePath` (see linkgit:git-config[1]). | |
455 | For Example: | |
456 | ||
457 | ------------ | |
458 | $ git worktree list --porcelain | |
459 | ... | |
460 | locked "reason\nwhy is locked" | |
461 | ... | |
bb9c03b8 MR |
462 | ------------ |
463 | ||
96454597 ES |
464 | EXAMPLES |
465 | -------- | |
466 | You are in the middle of a refactoring session and your boss comes in and | |
467 | demands that you fix something immediately. You might typically use | |
468 | linkgit:git-stash[1] to store your changes away temporarily, however, your | |
bc483285 MH |
469 | working tree is in such a state of disarray (with new, moved, and removed |
470 | files, and other bits and pieces strewn around) that you don't want to risk | |
471 | disturbing any of it. Instead, you create a temporary linked working tree to | |
96454597 ES |
472 | make the emergency fix, remove it when done, and then resume your earlier |
473 | refactoring session. | |
474 | ||
475 | ------------ | |
cbdf60fa | 476 | $ git worktree add -b emergency-fix ../temp master |
96454597 ES |
477 | $ pushd ../temp |
478 | # ... hack hack hack ... | |
479 | $ git commit -a -m 'emergency fix for boss' | |
480 | $ popd | |
3f0b42bd | 481 | $ git worktree remove ../temp |
96454597 ES |
482 | ------------ |
483 | ||
6d3824cf ES |
484 | BUGS |
485 | ---- | |
18b22dbe JH |
486 | Multiple checkout in general is still experimental, and the support |
487 | for submodules is incomplete. It is NOT recommended to make multiple | |
488 | checkouts of a superproject. | |
6d3824cf | 489 | |
df0b6cfb NTND |
490 | GIT |
491 | --- | |
492 | Part of the linkgit:git[1] suite |