blob: 5bede9ac22d260d703c5632f44ffc404013650d0 [file] [log] [blame]
git-repo-config - Get and set repository or global options.
'git-repo-config' [--global] [type] name [value [value_regex]]
'git-repo-config' [--global] [type] --replace-all name [value [value_regex]]
'git-repo-config' [--global] [type] --get name [value_regex]
'git-repo-config' [--global] [type] --get-all name [value_regex]
'git-repo-config' [--global] [type] --unset name [value_regex]
'git-repo-config' [--global] [type] --unset-all name [value_regex]
'git-repo-config' [--global] -l | --list
You can query/set/replace/unset options with this command. The name is
actually the section and the key separated by a dot, and the value will be
If you want to set/unset an option which can occur on multiple
lines, a POSIX regexp `value_regex` needs to be given. Only the
existing values that match the regexp are updated or unset. If
you want to handle the lines that do *not* match the regex, just
prepend a single exclamation mark in front (see EXAMPLES).
The type specifier can be either '--int' or '--bool', which will make
'git-repo-config' ensure that the variable(s) are of the given type and
convert the value to the canonical form (simple decimal number for int,
a "true" or "false" string for bool). If no type specifier is passed,
no checks or transformations are performed on the value.
This command will fail if:
. The .git/config file is invalid,
. Can not write to .git/config,
. no section was provided,
. the section or key is invalid,
. you try to unset an option which does not exist,
. you try to unset/set an option for which multiple lines match, or
. you use --global option without $HOME being properly set.
Default behavior is to replace at most one line. This replaces
all lines matching the key (and optionally the value_regex).
Get the value for a given key (optionally filtered by a regex
matching the value). Returns error code 1 if the key was not
found and error code 2 if multiple key values were found.
Like get, but does not fail if the number of values for the key
is not exactly one.
Like --get-all, but interprets the name as a regular expression.
Use global ~/.gitconfig file rather than the repository .git/config.
Remove the line matching the key from config file.
Remove all matching lines from config file.
-l, --list::
List all variables set in config file.
git-repo-config will ensure that the output is "true" or "false"
git-repo-config will ensure that the output is a simple decimal number
Take the configuration from the given file instead of .git/config.
Using the "--global" option forces this to ~/.gitconfig.
Currently the same as $GIT_CONFIG; when Git will support global
configuration files, this will cause it to take the configuration
from the global configuration file in addition to the given file.
Given a .git/config like this:
# This is the config file, and
# a '#' or ';' character indicates
# a comment
; core variables
; Don't trust file modes
filemode = false
; Our diff algorithm
external = "/usr/local/bin/gnu-diff -u"
renames = true
; Proxy settings
gitproxy="ssh" for "ssh://"
gitproxy="proxy-command" for
gitproxy="myprotocol-command" for "my://"
gitproxy=default-proxy ; for all the rest
you can set the filemode to true with
% git repo-config core.filemode true
The hypothetical proxy command entries actually have a postfix to discern
what URL they apply to. Here is how to change the entry for
to "ssh".
% git repo-config core.gitproxy '"ssh" for' 'for$'
This makes sure that only the key/value pair for is replaced.
To delete the entry for renames, do
% git repo-config --unset diff.renames
If you want to delete an entry for a multivar (like core.gitproxy above),
you have to provide a regex matching the value of exactly one line.
To query the value for a given key, do
% git repo-config --get core.filemode
% git repo-config core.filemode
or, to query a multivar:
% git repo-config --get core.gitproxy "for$"
If you want to know all the values for a multivar, do:
% git repo-config --get-all core.gitproxy
If you like to live dangerous, you can replace *all* core.gitproxy by a
new one with
% git repo-config --replace-all core.gitproxy ssh
However, if you really only want to replace the line for the default proxy,
i.e. the one without a "for ..." postfix, do something like this:
% git repo-config core.gitproxy ssh '! for '
To actually match only values with an exclamation mark, you have to
% git repo-config section.key value '[!]'
Written by Johannes Schindelin <>
Documentation by Johannes Schindelin, Petr Baudis and the git-list <>.
Part of the gitlink:git[7] suite