Identifiers & Environment Variables Flashcards
Memorize Git identifiers and environment variables so you'll never have to look them up again.
What does the following Git identifier or environment variable do:
< object >
Indicates the object name for any type of object.
What does the following Git identifier or environment variable do:
< blob >
Indicates a blob object name.
What does the following Git identifier or environment variable do:
< tree >
Indicates a tree object name.
What does the following Git identifier or environment variable do:
< commit >
Indicates a commit object name.
What does the following Git identifier or environment variable do:
< tree-ish >
Indicates a tree, commit or tag object name. A command that takes a argument ultimately wants to operate on a object but automatically dereferences and objects that point at a.
What does the following Git identifier or environment variable do:
< commit-ish >
Indicates a commit or tag object name. A command that takes a argument ultimately wants to operate on a object but automatically dereferences objects that point at a.
What does the following Git identifier or environment variable do:
< type >
Indicates that an object type is required. Currently one of: blob, tree, commit, or tag.
What does the following Git identifier or environment variable do:
< file >
Indicates a filename - almost always relative to the root of the tree structure GIT_INDEX_FILE describes.
What does the following Git identifier or environment variable do:
GIT_INDEX_FILE
This environment allows the specification of an alternate index file. If not specified, the default of $GIT_DIR/index is used.
What does the following Git identifier or environment variable do:
GIT_OBJECT_DIRECTORY
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.
What does the following Git identifier or environment variable do:
GIT_ALTERNATE_OBJECT_DIRECTORIES
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.
What does the following Git identifier or environment variable do:
GIT_DIR
If the GIT_DIR environment variable is set then it specifies a path to use instead of the default .git for the base of the repository.
What does the following Git identifier or environment variable do:
GIT_WORK_TREE
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.
What does the following Git identifier or environment variable do:
GIT_CEILING_DIRECTORIES
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.)
What does the following Git identifier or environment variable do:
GIT_DISCOVERY_ACROSS_FILESYSTEM
When run in a directory that does not have “.git” repository directory, git tries to find such a directory in the parent directories to find the top of the working tree, but by default it does not cross filesystem boundaries. This environment variable can be set to true to tell git not to stop at filesystem boundaries.
LikeGIT_CEILING_DIRECTORIES, this will not affect an explicit repository directory set via GIT_DIR or on the command line.
What does the following Git identifier or environment variable do:
GIT_MERGE_VERBOSITY
A number controlling the amount of output shown by the recursive merge strategy. Overrides merge.verbosity. See git-merge(1)