![]() ![]() You can limit which configuration sources are read from or written toīy specifying the path of a file with the -file option, or by git config will only ever change one file at a time. Taken then all values of a key from all files will be used.īy default, options are only written to the repository specificĬonfiguration file. Taking precedence over values read earlier. The files are read in the order given above, with last value found An error message is produced if the file is unreadable, but not Is missing or unreadable, git config will exit with a non-zero errorĬode. The global or the system-wide configuration files are missing or Options will be read from all of these files that are available. You may also provide additional configuration parameters when runningĪny git command by using the -c option. ![]() This is optional and is only searched whenĮxtensions.worktreeConfig is present in $GIT_DIR/config. If both filesĮxist, both files are read in the order given above. These are also called "global" configuration files. When the XDG_CONFIG_HOME environment variable is not set orĮmpty, $HOME/.config/ is used as $XDG_CONFIG_HOME. in the official documentation:īy default, git config will read configuration options from multipleįiles. It is stated how the path is determined e.g. The well-known/expected/normal way this happens is that USERPROFILE and all point to the network drive and trying to use programs offline simply produces hard errors (there is no automatic fallback to a different path). gitconfig to reside on network drives, but none of them noted the location to move around. Other people have reported their global.I have colleagues who claim it does not happen on their machines, even though nominally those should be configured identically.viminfo created whenever I dare to use Git at the wrong time.) (And indeed, outside of git, no program seems to automatically put files onto H: - there is only what I put there manually and vestigial files. group policies) in place, that could explain (aka cause) this behaviour. The respective IT departments providing either affected machine claimed to not have any configuration (e.g.(I no longer have access to the older one, but I think it had about 2.24.x.windows.y. ![]()
0 Comments
Leave a Reply. |