Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- Command-line interface conventions
- Everyday Git
- Frequently Asked Questions (FAQ)
- All guides...
The author of a piece of code.
The person who put a piece of code into Git.
Text editor for use by Git commands. The value is meant to be interpreted by the shell when it is used. Examples:
"C:\Program Files\Vim\gvim.exe" --nofork. The order of preference is the
$GIT_EDITORenvironment variable, then
$EDITOR, and then the default chosen at compile time, which is usually vi.
Text editor used to edit the todo file while running
git rebase -i. Like
GIT_EDITOR, the value is meant to be interpreted by the shell when it is used. The order of preference is the
$GIT_SEQUENCE_EDITORenvironment variable, then
sequence.editorconfiguration, and then the value of
git var GIT_EDITOR.
Text viewer for use by Git commands (e.g., less). The value is meant to be interpreted by the shell. The order of preference is the
$GIT_PAGERenvironment variable, then
$PAGER, and then the default chosen at compile time (usually less).
The name of the first branch created in newly initialized repositories.
The path of the binary providing the POSIX shell for commands which use the shell.
The path to the system gitattributes file, if one is enabled.
The path to the global (per-user) gitattributes file.
The path to the system configuration file, if one is enabled.
The path to the global (per-user) configuration files, if any.
Most path values contain only one value. However, some can contain multiple values, which are separated by newlines, and are listed in order from highest to lowest priority. Callers should be prepared for any such path value to contain multiple items.
Note that paths are printed even if they do not exist, but not if they are disabled by other environment variables.
Part of the git suite