Now you’ll learn a few of the more interesting options that you can set in this manner to customize your Git usage. First, a quick review: Git uses a series of configuration files to determine non-default …

If the repository configuration file is missing or unreadable, git config will exit with a non-zero error code. An error message is produced if the file is unreadable, but not if it is missing.

Git comes with a tool called git config that lets you get and set configuration variables that control all aspects of how Git looks and operates. These variables can be stored in three different places:

The files .git/config and optionally config.worktree (see extensions.worktreeConfig below) in each repository are used to store the configuration for that repository, and $HOME/.gitconfig is used to …

The Git configuration file contains a number of variables that affect the Git commands' behavior. The .git/config file in each repository is used to store the configuration for that repository, and …

The Git configuration file contains a number of variables that affect the Git commands' behavior. The .git/config file in each repository is used to store the configuration for that repository, and …

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.

If GIT_CONFIG_SYSTEM is set, the system config file defined at build time (usually /etc/gitconfig) will not be read. Likewise, if GIT_CONFIG_GLOBAL is set, neither $HOME/.gitconfig nor …

The file format of the shared-credential file is the same as that used by git-credential-store. The location of that file is fairly standard, but we should allow the user to pass a custom path just in case.

This command stores credentials indefinitely on disk for use by future Git programs. You probably don’t want to invoke this command directly; it is meant to be used as a credential helper by other parts of …