Путеводитель по Руководству Linux

  User  |  Syst  |  Libr  |  Device  |  Files  |  Other  |  Admin  |  Head  |



   git-worktree    ( 1 )

управляйте несколькими рабочими деревьями (Manage multiple working trees)

  Name  |  Synopsis  |  Description  |  Commands  |  Options  |  Refs  |    Config file    |  Details  |  List output format  |  Examples  |  Bugs  |

Конфигурационный файл (Config file)

By default, the repository config file is shared across all
       working trees. If the config variables core.bare or core.worktree
       are already present in the config file, they will be applied to
       the main working trees only.

In order to have configuration specific to working trees, you can turn on the worktreeConfig extension, e.g.:

$ git config extensions.worktreeConfig true

In this mode, specific configuration stays in the path pointed by git rev-parse --git-path config.worktree. You can add or update configuration in this file with git config --worktree. Older Git versions will refuse to access repositories with this extension.

Note that in this file, the exception for core.bare and core.worktree is gone. If they exist in $GIT_DIR/config, you must move them to the config.worktree of the main working tree. You may also take this opportunity to review and move other configuration that you do not want to share to all working trees:

core.worktree and core.bare should never be shared

core.sparseCheckout is recommended per working tree, unless you are sure you always use sparse checkout for all working trees.