Git comes with this handy tool that let’s you manage your Git configuration with ease.

Configuration Levels

  • --local

    (Default) Local configuration values are stored and managed at the repository level. The values are stored in a file found in the repo’s .git directory: .git/config

    If you are planning to set some configuration only to be used by the specific repo you are in, then go ahead with using --local.

    git config --local ""
  • --global

    Global configuration is one level above Local. These configuration are user-specific and managed through the .gitconfig file in user’s home directory: ~/.gitconfig

    If you want your configuration to reflect to all your repo’s in the system, then go ahead with using --global

    git config --global ""
  • --system

    System-level configuration applies to every user on the system, which means if none of the the local or the global values overrides the system level Git configuration value will be used. These configurations are true for all the repos' in the system and is managed through the /etc/gitconfig file.

    git config --system ""

Listing all the configurations

  • To see all the configuration values, use the command:

    git config --list
  • It can get quite messy when you have configuration values coming from multiple sources. To see the origin of the value as well add --show-origin

    git config --list --show-origin

Your Identity

The first chore the you always need to do after setting up Git is setting up your user name and email address. This is required because Git attaches this piece of information to ever changeset that you create in Git, known as Git commit.

Which level of configuration should we use? Because the details are user specific in most cases, the optimum answer is --global

git config --global "Sayan Chowdhury"
git config --global ""

Let’s verify this in the global settings file:

$ cat ~/.gitconfig
    name = Sayan Chowdhury
	email =

What are the other alternative will you use to verify?

Your Editor

Git invokes the editor for a lot of command for example while doing a commit, or rebasing your commits. When you type these commands it’s fire up the editor infront of you. Now, each of us has their own choice of editor so vim gives you option to configure which editor you would like to use.

I’m a vim user, thus for me the command would be:

git config --global core.editor "vim"

Colors in Git

Coming soon

Merge and diff tools

Coming soon

Git configurations you might find useful

More details on the following config coming soon

  • alias
  • commit.template
  • core.excludesfile
  • gpg.program
  • help.autocorrect
  • http.cookiefile
  • push.current
  • user.signingkey

To more on git config, read man git-config