git-commit-graph(1)

NAME#

git-commit-graph - Write and verify Git commit-graph files

SYNOPSIS#

git commit-graph verify\n [--object-dir <dir>] [--shallow] [--[no-]progress]
\ngit commit-graph write\n [--object-dir <dir>] [--append]
\n
                        [--split[=<strategy>]] [--reachable | --stdin-packs | --stdin-commits]
\n
                        [--changed-paths] [--[no-]max-new-filters <n>] [--[no-]progress]
\n
                        <split-options>

DESCRIPTION#

Manage the serialized commit-graph file.

OPTIONS#

--object-dir

--[no-]progress

COMMANDS#

write

With the --stdin-packs option, generate the new commit graph by walking objects only in the specified pack-indexes. (Cannot be combined with --stdin-commits or --reachable.)

With the --stdin-commits option, generate the new commit graph by walking commits starting at the commits specified in stdin as a list of OIDs in hex, one OID per line. OIDs that resolve to non-commits (either directly, or by peeling tags) are silently ignored. OIDs that are malformed, or do not exist generate an error. (Cannot be combined with --stdin-packs or --reachable.)

With the --reachable option, generate the new commit graph by walking commits starting at all refs. (Cannot be combined with --stdin-commits or --stdin-packs.)

With the --append option, include all commits that are present in the existing commit-graph file.

With the --changed-paths option, compute and write information about the paths changed between a commit and its first parent. This operation can take a while on large repositories. It provides significant performance gains for getting history of a directory or a file with git log -- <path>. If this option is given, future commit-graph writes will automatically assume that this option was intended. Use --no-changed-paths to stop storing this data.

With the --max-new-filters=<n> option, generate at most n new Bloom filters (if --changed-paths is specified). If n is -1, no limit is enforced. Only commits present in the new layer count against this limit. To retroactively compute Bloom filters over earlier layers, it is advised to use --split=replace. Overrides the commitGraph.maxNewFilters configuration.

With the --split[=<strategy>] option, write the commit-graph as a chain of multiple commit-graph files stored in <dir>/info/commit-graphs. Commit-graph layers are merged based on the strategy and other splitting options. The new commits not already in the commit-graph are added in a new "tip" file. This file is merged with the existing file if the following merge conditions are met:

Finally, if --expire-time=<datetime> is not specified, let datetime be the current time. After writing the split commit-graph, delete all unused commit-graph whose modified times are older than datetime.

verify

With the --shallow option, only check the tip commit-graph file in a chain of split commit-graphs.

EXAMPLES#

$ git commit-graph write

$ echo <pack-index> | git commit-graph write --stdin-packs

$ git show-ref -s | git commit-graph write --stdin-commits

$ git rev-parse HEAD | git commit-graph write --stdin-commits --append

CONFIGURATION#

Everything below this line in this section is selectively included from the git-config(1) documentation. The content is the same as what’s found there:

commitGraph.generationVersion

commitGraph.maxNewFilters

commitGraph.readChangedPaths

commitGraph.changedPathsVersion

Defaults to -1.

If -1, Git will use the version of the changed-path Bloom filters in the repository, defaulting to 1 if there are none.

If 0, Git will not read any Bloom filters, and will write version 1 Bloom filters when instructed to write.

If 1, Git will only read version 1 Bloom filters, and will write version 1 Bloom filters.

If 2, Git will only read version 2 Bloom filters, and will write version 2 Bloom filters.

See git-commit-graph(1) for more information.

FILE FORMAT#

see gitformat-commit-graph(5).

GIT#

Part of the git(1) suite