| 1 | `worktree.guessRemote`:: |
| 2 | If no branch is specified and neither `-b` nor `-B` nor |
| 3 | `--detach` is used, then `git worktree add` defaults to |
| 4 | creating a new branch from HEAD. If `worktree.guessRemote` is |
| 5 | set to true, `worktree add` tries to find a remote-tracking |
| 6 | branch whose name uniquely matches the new branch name. If |
| 7 | such a branch exists, it is checked out and set as "upstream" |
| 8 | for the new branch. If no such match can be found, it falls |
| 9 | back to creating a new branch from the current `HEAD`. |
| 10 | |
| 11 | `worktree.useRelativePaths`:: |
| 12 | Link worktrees using relative paths (when "`true`") or absolute |
| 13 | paths (when "`false`"). This is particularly useful for setups |
| 14 | where the repository and worktrees may be moved between |
| 15 | different locations or environments. Defaults to "`false`". |
| 16 | + |
| 17 | Note that setting `worktree.useRelativePaths` to "`true`" implies enabling the |
| 18 | `extensions.relativeWorktrees` config (see linkgit:git-config[1]), |
| 19 | thus making it incompatible with older versions of Git. |