b7016344f1
This introduces the `--[no-]relative-paths` CLI option and `worktree.useRelativePaths` configuration setting to the `worktree add` command. When enabled these options allow worktrees to be linked using relative paths, enhancing portability across environments where absolute paths may differ (e.g., containerized setups, shared network drives). Git still creates absolute paths by default, but these options allow users to opt-in to relative paths if desired. The t2408 test file is removed and more comprehensive tests are written for the various worktree operations in their own files. Signed-off-by: Caleb White <cdwhite3@pm.me> Signed-off-by: Junio C Hamano <gitster@pobox.com>
20 lines
973 B
Plaintext
20 lines
973 B
Plaintext
worktree.guessRemote::
|
|
If no branch is specified and neither `-b` nor `-B` nor
|
|
`--detach` is used, then `git worktree add` defaults to
|
|
creating a new branch from HEAD. If `worktree.guessRemote` is
|
|
set to true, `worktree add` tries to find a remote-tracking
|
|
branch whose name uniquely matches the new branch name. If
|
|
such a branch exists, it is checked out and set as "upstream"
|
|
for the new branch. If no such match can be found, it falls
|
|
back to creating a new branch from the current HEAD.
|
|
|
|
worktree.useRelativePaths::
|
|
Link worktrees using relative paths (when "true") or absolute
|
|
paths (when "false"). This is particularly useful for setups
|
|
where the repository and worktrees may be moved between
|
|
different locations or environments. Defaults to "false".
|
|
+
|
|
Note that setting `worktree.useRelativePaths` to "true" implies enabling the
|
|
`extension.relativeWorktrees` config (see linkgit:git-config[1]),
|
|
thus making it incompatible with older versions of Git.
|