$ git worktree add --track -b <branch> <path> <remote>/<branch>
------------
+
+ For best results it is advised to specify _<path>_ outside of the repository
+ and existing worktrees - see <<EXAMPLES,EXAMPLES>>
+ +
If the branch exists in multiple remotes and one of them is named by
the `checkout.defaultRemote` configuration variable, we'll use that
-one for the purposes of disambiguation, even if the `<branch>` isn't
+one for the purposes of disambiguation, even if the _<branch>_ isn't
unique across all remotes. Set it to
e.g. `checkout.defaultRemote=origin` to always checkout remote
-branches from there if `<branch>` is ambiguous but exists on the
+branches from there if _<branch>_ is ambiguous but exists on the
`origin` remote. See also `checkout.defaultRemote` in
linkgit:git-config[1].
+
$ git worktree remove ../temp
------------
+ Side by side branch checkouts for a repository using multiple worktrees
+
+ ------------
+ mkdir some-repository
+ cd some-repository
+ git clone --bare gitforge@someforge.example.com:some-org/some-repository some-repository.git
+ git --git-dir=some-repository.git worktree add some-branch
+ git --git-dir=some-repository.git worktree add another-branch
+ ------------
+
+CONFIGURATION
+-------------
+
+include::includes/cmd-config-section-all.adoc[]
+
+include::config/worktree.adoc[]
+
BUGS
----
Multiple checkout in general is still experimental, and the support