Git config
Internal
Overview
git config is used to manipulate entries in Git's configuration files. There are three levels of configuration files, listed below from the highest precedence to the lowest:
1. file (.git/config). This file contains repository-specific configuration and has the highest precedence. Repository-specific configuration is manipulated when git config is gets the "--file" option. This is the default.
2. global (~/.gitconfig). This file contains user-specific configuration and it is manipulated when git config gets the "--global" option.
3. system (/etc/gitconfig). This file contains system-wide configuration and can be manipulated with the "--system" option, if the user has proper permissions.
The configuration files are not replicated during git clone.
More info:
git config --help
Configuration Operations
List the Configuration
git config -l
Configure a Setting
git config [--file|--global|--system] <some.git.option> <value>
Remove a Setting
git config --unset [--file|--global|--system] <some.git.option>
Recipes
Configure the Commit Author
git config user.name "Ovidiu Feodorov" git config user.email "ovidiu@feodorov.com"
The same effect can be achieved by setting [GIT_AUTHOR_NAME|gitVariables#GIT_AUTHOR_NAME]/[GIT_AUTHOR_EMAIL|gitVariables#GIT_AUTHOR_EMAIL] environment variables.
To configure it for all repositories the user interacts with (if set on a specific repository, that setting will take precedence):
{{{ git config --global user.name "Ovidiu Feodorov" git config --global user.email "ovidiu@feodorov.com" }}}
!!!Configuring an Alias
{{{ git config --global alias.show-graph 'log --graph --abbrev-commit --pretty=oneline' }}}
!!!push.default
This setting affects the behavior of your local client and only when you don't specify which branches you want to push.
It can have two values: "matching" and "simple".
"matching" means Template:Git push with no argument will push all local branches to the ones with the same name on the remote. You don't need to establish any special link between the local branch and the remote branch.
This also makes it easy to accidentally push a branch you didn't intend to.
"simple" means git push will push only the current branch to the one that git pull would pull from (the link between the local branch and remote branch is established in ...) and also checks that their names match. This is a more intuitive behavior, which is why the default in Git 2.0 is getting changed to this.
Recommended value is "simple" - it is safer.
!!!Remote Manipulation
TODO
Organizatorium
git config --global http.sslVerify true|false