Git Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 16: Line 16:


=Files=
=Files=
* <code>[[/etc/gitconfig]]</code>
* <code>[[/etc/gitconfig#Overview|/etc/gitconfig]]</code>
* <code>[[.gitconfig]]</code>
* <code>[[.gitconfig]]</code>
* <code>[[.git/config]]</code>
* <code>[[.git/config]]</code>

Revision as of 22:12, 9 January 2024

Internal

Overview

Git maintains configuration in a hierarchy of files that includes system-wide configuration stored in /etc/gitconfig, user-specific configuration stored in ~/.gitconfig or ~/.config/git/config and repository specific configuration in stored in .git/config.



/etc/gitconfig contains configuration that applies to all users of the system. git config --system ... reads and writes this file. User-specific configuration is read and written with git config --global .... Repository specific configuration is read and written with git config --local .... If no option is specified, --local is the default.

If specified in multiple location, a configuration element is resolved to the most specific value: a repository-level value takes precedence over a user-level values, and a user-level value takes precedence over the corresponding system-level value. To use the effective value of a configuration element, use git config --get.

The configuration files are plain-text, so values can be set manually by editing the file and inserting the correct syntax. It’s generally easier to run the git config command, though.

Files

Environment Variables

Git Environment Variables

Configuration Options

Git Configuration Options

Configuration Operations

git config Configuration Operations