If you want to see a list of all the options your version of Git recognizes, you can run Many options are useful only in edge cases that I won’t go over here. Although tons of options are available, I’ll only cover the few that either are commonly used or can significantly affect your workflow. The majority of the options are client side-configuring your personal working preferences. The configuration options recognized by Git fall into two categories: client side and server side. You can also set these values by manually editing the file and inserting the correct syntax, but it’s generally easier to run the command. git/config trump those in /etc/gitconfig, for instance. Each level overwrites values in the previous level, so values in. These values are specific to that single repository. git/config ) of whatever repository you’re currently using. You can make Git read and write to this file by passing the option.įinally, Git looks for configuration values in the config file in the Git directory (. The next place Git looks is the ~/.gitconfig file, which is specific to each user. If you pass the option -system to git config, it reads and writes from this file specifically.

Is in an /etc/gitconfig file, which contains values for every user on the system and all of their repositories. The first place Git looks for these values Git uses a series of configuration files to determine non-default behavior that you may want. You saw some simple Git configuration details in the first chapter, but I’ll go over them again quickly here. $ git config -global user.email you’ll learn a few of the more interesting options that you can set in this manner to customize your Git usage. $ git config -global user.name 'John Doe' One of the first things you did was set up your name and e-mail address:

As you briefly saw in the Chapter 1, you can specify Git configuration settings with the git config command.

Setup git on mac