Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 2.23.0 08/16/19
- 2.22.1 08/11/19
- 2.22.0 06/07/19
- 2.21.0 02/24/19
- 2.20.1 no changes
- 2.20.0 12/09/18
- 2.19.2 11/21/18
- 2.19.1 09/27/18
- 2.19.0 09/10/18
- 2.18.1 no changes
- 2.18.0 06/21/18
- 2.17.1 → 2.17.2 no changes
- 2.17.0 04/02/18
- 2.16.5 no changes
- 2.16.4 05/22/18
- 2.16.1 no changes
- 2.16.0 01/17/18
- 2.15.3 no changes
- 2.15.2 05/22/18
- 2.14.4 → 2.14.5 no changes
- 2.14.3 10/23/17
- 2.14.2 09/22/17
- 2.13.3 → 2.14.0 no changes
- 2.13.2 06/24/17
- 2.12.4 → 2.12.5 no changes
- 2.12.3 05/05/17
- 2.12.2 03/24/17
- 2.12.1 03/20/17
- 2.12.0 02/24/17
- 2.11.3 → 2.11.4 no changes
- 2.11.2 05/05/17
- 2.11.1 02/02/17
- 2.11.0 11/29/16
- 2.10.4 → 2.10.5 no changes
- 2.10.3 05/05/17
- 2.10.2 10/28/16
- 2.9.5 no changes
- 2.9.4 05/05/17
- 2.9.3 08/12/16
- 2.9.1 07/11/16
- 2.9.0 06/13/16
- 2.8.6 no changes
- 2.8.5 05/05/17
- 2.8.4 06/06/16
- 2.8.3 05/18/16
- 2.8.2 04/29/16
- 2.8.0 03/28/16
- 2.7.6 no changes
- 2.7.5 05/05/17
- 2.7.4 03/17/16
- 2.7.3 03/10/16
- 2.7.2 02/22/16
- 2.7.0 01/04/16
- 2.6.7 05/05/17
- 2.6.6 03/17/16
- 2.6.5 01/04/16
- 2.6.1 09/29/15
- 2.6.0 09/28/15
- 2.5.6 05/05/17
- 2.5.5 03/17/16
- 2.5.4 09/28/15
- 2.5.2 09/04/15
- 2.5.1 08/28/15
- 2.4.12 05/05/17
- 2.4.11 03/17/16
- 2.4.10 09/28/15
- 2.4.9 09/04/15
- 2.4.8 08/03/15
- 2.4.7 07/27/15
- 2.4.6 07/15/15
- 2.4.5 06/25/15
- 2.4.4 06/16/15
- 2.4.2 05/26/15
- 2.4.1 05/13/15
- 2.4.0 04/30/15
- 2.3.10 09/28/15
- 2.3.9 09/04/15
- 2.3.8 05/11/15
- 2.3.6 04/21/15
- 2.3.5 03/31/15
- 2.3.4 03/23/15
- 2.3.3 03/14/15
- 2.3.2 03/06/15
- 2.3.1 02/25/15
- 2.3.0 02/05/15
- 2.2.3 09/04/15
- 2.2.2 01/12/15
- 2.2.1 12/17/14
- 2.2.0 11/26/14
git [--version] [--exec-path[=GIT_EXEC_PATH]] [--html-path] [-p|--paginate|--no-pager] [--no-replace-objects] [--bare] [--git-dir=GIT_DIR] [--work-tree=GIT_WORK_TREE] [--help] COMMAND [ARGS]
Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals.
See gittutorial to get started, then see Everyday Git for a useful minimum set of commands, and "man git-commandname" for documentation of each command. CVS users may also want to read gitcvs-migration. See the Git User’s Manual for a more in-depth introduction.
The COMMAND is either a name of a Git command (see below) or an alias as defined in the configuration file (see git-config).
Formatted and hyperlinked version of the latest git
documentation can be viewed at
Prints the git suite version that the git program came from.
Prints the synopsis and a list of the most commonly used commands. If the option --all or -a is given then all available commands are printed. If a git command is named this option will bring up the manual page for that command.
Other options are available to control how the manual page is displayed. See git-help for more information, because
git --help ...is converted internally into
git help ....
Path to wherever your core git programs are installed. This can also be controlled by setting the GIT_EXEC_PATH environment variable. If no path is given, git will print the current setting and then exit.
Print the path to wherever your git HTML documentation is installed and exit.
Pipe all output into less (or if set, $PAGER).
Do not pipe git output into a pager.
Set the path to the repository. This can also be controlled by setting the GIT_DIR environment variable. It can be an absolute path or relative path to current working directory.
Set the path to the working tree. The value will not be used in combination with repositories found automatically in a .git directory (i.e. $GIT_DIR is not set). This can also be controlled by setting the GIT_WORK_TREE environment variable and the core.worktree configuration variable. It can be an absolute path or relative path to the directory specified by --git-dir or GIT_DIR. Note: If --git-dir or GIT_DIR are specified but none of --work-tree, GIT_WORK_TREE and core.worktree is specified, the current working directory is regarded as the top directory of your working tree.
Treat the repository as a bare repository. If GIT_DIR environment is not set, it is set to the current working directory.
Do not use replacement refs to replace git objects. See git-replace for more information.
See the references above to get started using git. The following is probably more detail than necessary for a first-time user.
See gitworkflows for an overview of recommended workflows.
See also the howto documents for some useful examples.
The internals are documented in the GIT API documentation.
We divide git into high level ("porcelain") commands and low level ("plumbing") commands.
We separate the porcelain commands into the main commands and some ancillary user utilities.
Add file contents to the index
Apply a series of patches from a mailbox
Create an archive of files from a named tree
Find by binary search the change that introduced a bug
List, create, or delete branches
Move objects and refs by archive
Checkout a branch or paths to the working tree
Apply the change introduced by an existing commit
Graphical alternative to git-commit
Remove untracked files from the working tree
Clone a repository into a new directory
Record changes to the repository
Show the most recent tag that is reachable from a commit
Show changes between commits, commit and working tree, etc
Download objects and refs from another repository
Prepare patches for e-mail submission
Cleanup unnecessary files and optimize the local repository
Print lines matching a pattern
A portable graphical interface to Git
Create an empty git repository or reinitialize an existing one
The git repository browser
Show commit logs
Join two or more development histories together
Move or rename a file, a directory, or a symlink
Add/inspect commit notes
Fetch from and merge with another repository or a local branch
Update remote refs along with associated objects
Forward-port local commits to the updated upstream head
Reset current HEAD to the specified state
Revert an existing commit
Remove files from the working tree and from the index
Summarize git log output
Show various types of objects
Stash the changes in a dirty working directory away
Show the working tree status
Initialize, update or inspect submodules
Create, list, delete or verify a tag object signed with GPG
Get and set repository or global options
Git data exporter
Backend for fast Git data importers
(deprecated) Recover lost refs that luckily have not yet been pruned
Run merge conflict resolution tools to resolve merge conflicts
Pack heads and tags for efficient repository access
Prune all unreachable objects from the object database
Manage reflog information
Hardlink common objects in local repositories
manage set of tracked repositories
Pack unpacked objects in a repository
Create, list, delete refs to replace objects
(deprecated) Get and set repository or global options
Annotate file lines with commit information
Show what revision and author last modified each line of a file
Find commits not merged upstream
Count unpacked number of objects and their disk consumption
Show changes using common diff tools
Verifies the connectivity and validity of the objects in the database
Extract commit ID from an archive created using git-archive
display help information about git
Instantly browse your working repository in gitweb
Show three-way merge without touching index
Reuse recorded resolution of conflicted merges
Pick out and massage parameters
Show branches and their commits
Check the GPG signature of tags
Show logs with difference each commit introduces
These commands are to interact with foreign SCM and with other people via patch over e-mail.
Import an Arch repository into git
Export a single commit to a CVS checkout
Salvage your data out of another SCM people love to hate
A CVS server emulator for git
Send a collection of patches from stdin to an IMAP folder
Applies a quilt patchset onto the current branch
Generates a summary of pending changes
Send a collection of patches as emails
Bidirectional operation between a Subversion repository and git
Although git includes its own porcelain layer, its low-level commands are sufficient to support development of alternative porcelains. Developers of such porcelains might start by reading about git-update-index and git-read-tree.
The interface (input, output, set of options and the semantics) to these low-level commands are meant to be a lot more stable than Porcelain level commands, because these commands are primarily for scripted use. The interface to Porcelain commands on the other hand are subject to change in order to improve the end user experience.
The following description divides the low-level commands into commands that manipulate objects (in the repository, index, and working tree), commands that interrogate and compare objects, and commands that move objects and references between repositories.
Apply a patch to files and/or to the index
Copy files from the index to the working tree
Create a new commit object
Compute object ID and optionally creates a blob from a file
Build pack index file for an existing packed archive
Run a three-way file merge
Run a merge for files needing merging
Creates a tag object
Build a tree-object from ls-tree formatted text
Create a packed archive of objects
Remove extra objects that are already in pack files
Reads tree information into the index
Read and modify symbolic refs
Unpack objects from a packed archive
Register file contents in the working tree to the index
Update the object name stored in a ref safely
Create a tree object from the current index
Provide content or type and size information for repository objects
Compares files in the working tree and the index
Compares content and mode of blobs between the index and repository
Compares the content and mode of blobs found via two tree objects
Output information on each ref
Show information about files in the index and the working tree
List references in a remote repository
List the contents of a tree object
Find as good common ancestors as possible for a merge
Find symbolic names for given revs
Find redundant pack files
Lists commit objects in reverse chronological order
Show packed archive index
List references in a local repository
(deprecated) Create a tar archive of the files in the named tree object
Creates a temporary file with a blob’s contents
Show a git logical variable
Validate packed git archive files
In general, the interrogate commands do not touch the files in the working tree.
A really simple server for git repositories
Receive missing objects from another repository
Server side implementation of Git over HTTP
Push objects over git protocol to another repository
Update auxiliary info file to help dumb servers
The following are helper commands used by the above; end users typically do not use them directly.
Download from a remote git repository via HTTP
Push objects over HTTP/DAV to another repository
Routines to help parsing remote repository access parameters
Receive what is pushed into the repository
Restricted login shell for GIT-only SSH access
Send archive back to git-archive
Send objects packed back to git-fetch-pack
These are internal helper commands used by other commands; end users typically do not use them directly.
Display gitattributes information
Ensures that a reference name is well formed
Produce a merge commit message
Extracts patch and authorship from a single e-mail message
Simple UNIX mbox splitter program
The standard helper program to use with git-merge-index
Compute unique ID for a patch
(deprecated) List the references in a remote repository
Common git shell script setup code
Filter out empty lines
Starting from 0.99.9 (actually mid 0.99.8.GIT),
is used to hold per-repository configuration options. It is a
simple text file modeled after
.ini format familiar to some
people. Here is an example:
# # A '#' or ';' character indicates a comment. # ; core variables [core] ; Don't trust file modes filemode = false ; user identity [user] name = "Junio C Hamano" email = "firstname.lastname@example.org"
Various commands read from the configuration file and adjust their operation accordingly.
Indicates the object name for any type of object.
Indicates a blob object name.
Indicates a tree object name.
Indicates a commit object name.
Indicates a tree, commit or tag object name. A command that takes a <tree-ish> argument ultimately wants to operate on a <tree> object but automatically dereferences <commit> and <tag> objects that point at a <tree>.
Indicates a commit or tag object name. A command that takes a <commit-ish> argument ultimately wants to operate on a <commit> object but automatically dereferences <tag> objects that point at a <commit>.
Indicates that an object type is required. Currently one of:
Indicates a filename - almost always relative to the root of the tree structure
Any git command accepting any <object> can also use the following symbolic notation:
For a more complete list of ways to spell object names, see "SPECIFYING REVISIONS" section in git-rev-parse.
Please see gitglossary.
Various git commands use the following environment variables:
These environment variables apply to all core git commands. Nb: it is worth noting that they may be used/overridden by SCMS sitting above git so take care if using Cogito etc.
This environment allows the specification of an alternate index file. If not specified, the default of
If the object storage directory is specified via this environment variable then the sha1 directories are created underneath - otherwise the default
$GIT_DIR/objectsdirectory is used.
Due to the immutable nature of git objects, old objects can be archived into shared, read-only directories. This variable specifies a ":" separated (on Windows ";" separated) list of git object directories which can be used to search for git objects. New objects will not be written to these directories.
If the GIT_DIR environment variable is set then it specifies a path to use instead of the default
.gitfor the base of the repository.
Set the path to the working tree. The value will not be used in combination with repositories found automatically in a .git directory (i.e. $GIT_DIR is not set). This can also be controlled by the --work-tree command line option and the core.worktree configuration variable.
This should be a colon-separated list of absolute paths. If set, it is a list of directories that git should not chdir up into while looking for a repository directory. It will not exclude the current working directory or a GIT_DIR set on the command line or in the environment. (Useful for excluding slow-loading network directories.)
Only valid setting is "--unified=??" or "-u??" to set the number of context lines shown when a unified diff is created. This takes precedence over any "-U" or "--unified" option value passed on the git diff command line.
When the environment variable GIT_EXTERNAL_DIFF is set, the program named by it is called, instead of the diff invocation described above. For a path that is added, removed, or modified, GIT_EXTERNAL_DIFF is called with 7 parameters:
path old-file old-hex old-mode new-file new-hex new-mode
are files GIT_EXTERNAL_DIFF can use to read the contents of <old|new>,
are the 40-hexdigit SHA1 hashes,
are the octal representation of the file modes.
The file parameters can point at the user’s working file (e.g.
old-filewhen a new file is added), or a temporary file (e.g.
old-filein the index). GIT_EXTERNAL_DIFF should not worry about unlinking the temporary file --- it is removed when GIT_EXTERNAL_DIFF exits.
For a path that is unmerged, GIT_EXTERNAL_DIFF is called with 1 parameter, <path>.
A number controlling the amount of output shown by the recursive merge strategy. Overrides merge.verbosity. See git-merge
This environment variable overrides
$PAGER. If it is set to an empty string or to the value "cat", git will not launch a pager. See also the
core.pageroption in git-config.
If this environment variable is set then git fetch and git push will use this command instead of ssh when they need to connect to a remote system. The $GIT_SSH command will be given exactly two arguments: the username@host (or just host) from the URL and the shell command to execute on that remote system.
To pass options to the program that you want to list in GIT_SSH you will need to wrap the program and options into a shell script, then set GIT_SSH to refer to the shell script.
Usually it is easier to configure any desired options through your personal
.ssh/configfile. Please consult your ssh documentation for further details.
If this environment variable is set to "1", then commands such as git blame (in incremental mode), git rev-list, git log, and git whatchanged will force a flush of the output stream after each commit-oriented record have been flushed. If this variable is set to "0", the output of these commands will be done using completely buffered I/O. If this environment variable is not set, git will choose buffered or record-oriented flushing based on whether stdout appears to be redirected to a file or not.
If this variable is set to "1", "2" or "true" (comparison is case insensitive), git will print
trace:messages on stderr telling about alias expansion, built-in command execution and external command execution. If this variable is set to an integer value greater than 1 and lower than 10 (strictly) then git will interpret this value as an open file descriptor and will try to write the trace messages into this file descriptor. Alternatively, if this variable is set to an absolute path (starting with a / character), git will interpret this as a file path and will try to write the trace messages into it.
A git project normally consists of a working directory with a ".git" subdirectory at the top level. The .git directory contains, among other things, a compressed object database representing the complete history of the project, an "index" file which links that history to the current contents of the working tree, and named pointers into that history such as tags and branch heads.
The object database contains objects of three main types: blobs, which hold file data; trees, which point to blobs and other trees to build up directory hierarchies; and commits, which each reference a single tree and some number of parent commits.
The commit, equivalent to what other systems call a "changeset" or "version", represents a step in the project’s history, and each parent represents an immediately preceding step. Commits with more than one parent represent merges of independent lines of development.
All objects are named by the SHA1 hash of their contents, normally written as a string of 40 hex digits. Such names are globally unique. The entire history leading up to a commit can be vouched for by signing just that commit. A fourth object type, the tag, is provided for this purpose.
When first created, objects are stored in individual files, but for efficiency may later be compressed together into "pack files".
Named pointers called refs mark interesting points in history. A ref
may contain the SHA1 name of an object or the name of another ref. Refs
with names beginning
ref/head/ contain the SHA1 name of the most
recent commit (or "head") of a branch under development. SHA1 names of
tags of interest are stored under
ref/tags/. A special ref named
HEAD contains the name of the currently checked-out branch.
The index file is initialized with a list of all paths and, for each path, a blob object and a set of attributes. The blob object represents the contents of the file as of the head of the current branch. The attributes (last modified time, size, etc.) are taken from the corresponding file in the working tree. Subsequent changes to the working tree can be found by comparing these attributes. The index may be updated with new content, and new commits may be created from the content stored in the index.
The index is also capable of storing multiple entries (called "stages") for a given pathname. These stages are used to hold the various unmerged version of a file when a merge is in progress.
Part of the git suite