Git - Git Configuration

Tags

Top Highlights

• If your computer is running macOS, you’re probably familiar with .DS_Store files. If your preferred editor is Emacs or Vim, you know about filenames that end with a ~ or .swp. This setting lets you write a kind of global .gitignore file. If you create a ~/.gitignore_global file with these contents:

• how Git works and how to use it, and we’ve introduced a number of tools that Git provides to help you use it easily and efficiently.

• how you can make Git operate in a more customized fashion, by introducing several important configuration settings and the hooks system. With these tools, it’s easy to get Git to work exactly the way you, your company, or your group needs it to.

• Git uses a series of configuration files to determine non-default behavior that you may want. The first place Git looks for these values is in the system-wide [path]/etc/gitconfig file, which contains settings that are applied to every user on the system and all of their repositories. If you pass the option --system to git config, it reads and writes from this file specifically.

• the ~/.gitconfig (or ~/.config/git/config) file, which is specific to each user. You can make Git read and write to this file by passing the --global option.

• Finally, Git looks for configuration values in the configuration file in the Git directory (.git/config) of whatever repository you’re currently using. These values are specific to that single repository, and represent passing the --local option to git config. If you don’t specify which level you want to work with, this is the default.

• client-side and server-side

• have Git not see them as untracked files or try to stage them when you run git add on them, as discussed in Ignoring Files.

• core.excludesfile