public final Class Constants

Binary value for custom merger.

Since

4.9

Union built-in merge driver

Since

6.10.1

Diff attribute.

Since

4.11

Key for filters in .gitattributes

Since

4.2

clean command name, used to call filter driver

Since

4.2

smudge command name, used to call filter driver

Since

4.2

Merge attribute.

Since

4.9

Builtin filter commands start with this prefix

Since

4.6

name of the file containing the ID of a cherry pick commit in case of conflicts

Prefix of a CMS signature (X.509, S/MIME).

Since

7.0

Name of the file in which git commands and hooks store and read the message prepared for the upcoming commit.

Since

4.0

If a commit-graph file was written by a version of Git that did not compute generation numbers, then those commits will have generation number represented by ().

Since

6.5

We use () as generation number for commits not in the commit-graph file.

Since

6.5

Name of the file (inside gitDir) that has reference to $GIT_COMMON_DIR. .git/worktrees/<worktree-name>/commondir If this file exists, $GIT_COMMON_DIR will be set to the path specified in this file unless it is explicitly set. If the specified path is relative, it is relative to $GIT_DIR. The repository with commondir is incomplete without the repository pointed by "commondir".

Since

7.0

Default name for the Git repository configuration

Default remote name used by clone, push and fetch operations

The default extension for local bundle files

Since

5.8

Default name for the Git repository directory

Name of the attributes file

Since

3.7

A bare repository typically ends with this string

Name of the ignore file

Name of the submodules file

Well-known object ID for the empty blob.

Since

0.9.1

Well-known object ID for the empty tree.

Since

5.1

Special name for the "FETCH_HEAD" symbolic-ref.

The environment variable that tells us where to look for objects, besides the default objects directory.

The environment variable that contains the author's email

The environment variable that contains the author's name

The environment variable that limits how close to the root of the file systems JGit will traverse when looking for a repository root.

The environment variable that contains the commiter's email

The environment variable that contains the commiter's name

The environment variable that tells us which directory is the common ".git" directory.

Since

7.0

The environment variable that blocks use of the system config file

Since

3.3

The environment variable that tells us which directory is the ".git" directory

The environment variable that tells us which file holds the Git index.

The environment variable that tells us where objects are stored

The environment variable that tells us which directory is the working directory.

Prefix of the first line in a ".git" file

Since

3.6

Name of the file (inside gitDir) that references the worktree's .git file (opposite link). .git/worktrees/<worktree-name>/gitdir A text file containing the absolute path back to the .git file that points here. This file is used to verify if the linked repository has been manually removed in which case this directory is no longer needed. The modification time (mtime) of this file should be updated each time the linked repository is accessed.

Since

7.0

A gitignore file name

Prefix of a GPG signature.

Since

7.0

Special name for the "HEAD" symbolic-ref.

Name of heads folder or file in refs.

Since

7.0

Name of the folder (inside gitDir) where the hooks are stored.

Since

3.7

Depth used to unshallow a repository

Since

6.3

Info alternates file (goes under OBJECTS)

Since

5.5

Attributes-override-file

Since

4.2

info commit-graph file (goes under OBJECTS)

Since

6.5

Excludes-file

Since

3.0

HTTP alternates file (goes under OBJECTS)

Since

5.5

Info refs folder

Prefix for any log.

Since

7.0

Suffix of lock file name

Since

4.7

Logs folder name

Default main branch name

name of the file containing the IDs of the parents of a merge commit

name of the file containing the commit msg for a merge commit

Name of the folder (inside gitDir) where submodules are stored

Since

3.6

An unknown or invalid object type code.

In-pack object type: blob.

Indicates the associated object is a blob.

This constant is fixed and is defined by the Git packfile format.

See Also

TYPE_BLOB

In-pack object type: commit.

Indicates the associated object is a commit.

This constant is fixed and is defined by the Git packfile format.

See Also

TYPE_COMMIT

In-pack object type: extended types.

This header code is reserved for future expansion. It is currently undefined/unsupported.

In-pack object type: offset delta

Objects stored with this type actually have a different type which must be obtained from their delta base object. Delta objects store only the changes needed to apply to the base object in order to recover the original object.

An offset delta uses a negative offset from the start of this object to refer to its delta base. The base object must exist in this packfile (even in the case of a thin pack).

This constant is fixed and is defined by the Git packfile format.

In-pack object type: reference delta

Objects stored with this type actually have a different type which must be obtained from their delta base object. Delta objects store only the changes needed to apply to the base object in order to recover the original object.

A reference delta uses a full object id (hash) to reference the delta base. The base object is allowed to be omitted from the packfile, but only in the case of a thin pack being transferred over the network.

This constant is fixed and is defined by the Git packfile format.

In-pack object type: annotated tag.

Indicates the associated object is an annotated tag.

This constant is fixed and is defined by the Git packfile format.

See Also

TYPE_TAG

In-pack object type: tree.

Indicates the associated object is a tree.

This constant is fixed and is defined by the Git packfile format.

See Also

TYPE_BLOB

In-pack object type: reserved for future use.

The historic length of an abbreviated Git object hash string. Git 2.11 changed this static number to a dynamically calculated one that scales as the repository grows.

Since

6.1

A Git object hash is 160 bits, i.e. 20 bytes.

Changing this assumption is not going to be as easy as changing this declaration.

A Git object can be expressed as a 40 character string of hexadecimal digits.

See Also

OBJECT_ID_LENGTH

Objects folder name

Since

5.5

name of the ref ORIG_HEAD used by certain commands to store the original value of HEAD

The system property that contains the system user name

Since

3.6

The system property that contains the system user name

Pack file signature that occurs at file header - identifies file as Git packfile formatted.

This constant is fixed and is defined by the Git packfile format.

Packed refs file

Prefix for branch refs

Prefix for notes refs

Standard notes ref

Prefix for any ref

Prefix for remotes refs

Standard stash ref

Prefix for tag refs

Reftable folder name

Since

5.6

name of the file containing the ID of a revert commit in case of conflicts

Name of the .git/shallow file

Beginning of the common "Signed-off-by: " commit message line

name of the file containing the commit msg for a squash commit

Prefix of an SSH signature.

Since

7.0

Default stash branch name

Reftable table list name.

Since

5.6.2

Text string that identifies an object as a blob.

Blobs store whole file revisions. They are used for any user file, as well as for symlinks. Blobs form the bulk of any project's storage space.

Text string that identifies an object as a commit.

Commits connect trees into a string of project histories, where each commit is an assertion that the best way to continue is to use this other tree (set of files).

Text string that identifies an object as an annotated tag.

Annotated tags store a pointer to any other object, and an additional message. It is most commonly used to record a stable release of the project.

Text string that identifies an object as a tree.

Trees attach object ids (hashes) to names and file modes. The normal use for a tree is to store a version of a directory and its contents.

Default value for the user name if no other information is available

The key of the XDG_CONFIG_HOME directory defined in the XDG Base Directory specification.

Since

5.5.2