Global configuration values are stored in a file that is located in a user's home directory. Global level configuration is user-specific, meaning it is applied to an operating system user. Local configuration values are stored in a file that can be found in the repo's. Local level configuration is applied to the context repository git config gets invoked in. The following configuration levels are available:īy default, git config will write to a local level if no configuration option is passed. The git config command can accept arguments to specify which configuration level to operate on. git config levels and filesīefore we further discuss git config usage, let's take a moment to cover configuration levels.

This will return the configured email address, if any, that Git will associate with locally created commits. In this example, email is a child property of the user configuration block. For example: user.email git config user.email Configuration names are dot delimited strings composed of a 'section' and a 'key' based on their hierarchy.

The most basic use case for git config is to invoke it with a configuration name, which will display the set value at that name. Becoming familiar with git config and the various Git configuration settings will help you create a powerful, customized Git workflow. We'll discuss Git aliases, which allow you to create shortcuts for frequently used Git operations. We'll be covering common configuration settings like email, username, and editor. Executing git config will modify a configuration text file. These configuration levels correspond to. The git config command is a convenience function that is used to set Git configuration values on a global or local project level. We briefly discussed git config usage on our Setting up a Repository page. In this document, we'll take an in-depth look at the git config command.

Get sublime for mac