1 extensions.objectFormat::
2 Specify the hash algorithm to use. The acceptable values are `sha1` and
3 `sha256`. If not specified, `sha1` is assumed. It is an error to specify
4 this key unless `core.repositoryFormatVersion` is 1.
6 Note that this setting should only be set by linkgit:git-init[1] or
7 linkgit:git-clone[1]. Trying to change it after initialization will not
8 work and will produce hard-to-diagnose issues.
10 extensions.worktreeConfig::
11 If enabled, then worktrees will load config settings from the
12 `$GIT_DIR/config.worktree` file in addition to the
13 `$GIT_COMMON_DIR/config` file. Note that `$GIT_COMMON_DIR` and
14 `$GIT_DIR` are the same for the main working tree, while other
15 working trees have `$GIT_DIR` equal to
16 `$GIT_COMMON_DIR/worktrees/<id>/`. The settings in the
17 `config.worktree` file will override settings from any other
20 When enabling `extensions.worktreeConfig`, you must be careful to move
21 certain values from the common config file to the main working tree's
22 `config.worktree` file, if present:
24 * `core.worktree` must be moved from `$GIT_COMMON_DIR/config` to
25 `$GIT_COMMON_DIR/config.worktree`.
26 * If `core.bare` is true, then it must be moved from `$GIT_COMMON_DIR/config`
27 to `$GIT_COMMON_DIR/config.worktree`.
29 It may also be beneficial to adjust the locations of `core.sparseCheckout`
30 and `core.sparseCheckoutCone` depending on your desire for customizable
31 sparse-checkout settings for each worktree. By default, the `git
32 sparse-checkout` builtin enables `extensions.worktreeConfig`, assigns
33 these config values on a per-worktree basis, and uses the
34 `$GIT_DIR/info/sparse-checkout` file to specify the sparsity for each
35 worktree independently. See linkgit:git-sparse-checkout[1] for more
38 For historical reasons, `extensions.worktreeConfig` is respected
39 regardless of the `core.repositoryFormatVersion` setting.