---

   git-config    ( 1 )

---

Окружение (Environment)

GIT_CONFIG_GLOBAL, GIT_CONFIG_SYSTEM
           Take the configuration from the given files instead from
           global or system-level configuration. See git(1) for details.

       GIT_CONFIG_NOSYSTEM
           Whether to skip reading settings from the system-wide
           $(prefix)/etc/gitconfig file. See git(1) for details.

       See also the section called 'FILES'.

       GIT_CONFIG_COUNT, GIT_CONFIG_KEY_<n>, GIT_CONFIG_VALUE_<n>
           If GIT_CONFIG_COUNT is set to a positive number, all
           environment pairs GIT_CONFIG_KEY_<n> and GIT_CONFIG_VALUE_<n>
           up to that number will be added to the process's runtime
           configuration. The config pairs are zero-indexed. Any missing
           key or value is treated as an error. An empty
           GIT_CONFIG_COUNT is treated the same as GIT_CONFIG_COUNT=0,
           namely no pairs are processed. These environment variables
           will override values in configuration files, but will be
           overridden by any explicit options passed via git -c.

           This is useful for cases where you want to spawn multiple git
           commands with a common configuration but cannot depend on a
           configuration file, for example when writing scripts.

       GIT_CONFIG
           If no --file option is provided to git config, use the file
           given by GIT_CONFIG as if it were provided via --file. This
           variable has no effect on other Git commands, and is mostly
           for historical compatibility; there is generally no reason to
           use it instead of the --file option.