6 git-commit-graph - Write and verify Git commit-graph files
12 'git commit-graph verify' [--object-dir <dir>] [--shallow] [--[no-]progress]
13 'git commit-graph write' <options> [--object-dir <dir>] [--[no-]progress]
19 Manage the serialized commit-graph file.
25 Use given directory for the location of packfiles and commit-graph
26 file. This parameter exists to specify the location of an alternate
27 that only has the objects directory, not a full `.git` directory. The
28 commit-graph file is expected to be in the `<dir>/info` directory and
29 the packfiles are expected to be in `<dir>/pack`. If the directory
30 could not be made into an absolute path, or does not match any known
31 object directory, `git commit-graph ...` will exit with non-zero
35 Turn progress on/off explicitly. If neither is specified, progress is
36 shown if standard error is connected to a terminal.
42 Write a commit-graph file based on the commits found in packfiles.
44 With the `--stdin-packs` option, generate the new commit graph by
45 walking objects only in the specified pack-indexes. (Cannot be combined
46 with `--stdin-commits` or `--reachable`.)
48 With the `--stdin-commits` option, generate the new commit graph by
49 walking commits starting at the commits specified in stdin as a list
50 of OIDs in hex, one OID per line. OIDs that resolve to non-commits
51 (either directly, or by peeling tags) are silently ignored. OIDs that
52 are malformed, or do not exist generate an error. (Cannot be combined
53 with `--stdin-packs` or `--reachable`.)
55 With the `--reachable` option, generate the new commit graph by walking
56 commits starting at all refs. (Cannot be combined with `--stdin-commits`
59 With the `--append` option, include all commits that are present in the
60 existing commit-graph file.
62 With the `--changed-paths` option, compute and write information about the
63 paths changed between a commit and its first parent. This operation can
64 take a while on large repositories. It provides significant performance gains
65 for getting history of a directory or a file with `git log -- <path>`. If
66 this option is given, future commit-graph writes will automatically assume
67 that this option was intended. Use `--no-changed-paths` to stop storing this
70 With the `--max-new-filters=<n>` option, generate at most `n` new Bloom
71 filters (if `--changed-paths` is specified). If `n` is `-1`, no limit is
72 enforced. Only commits present in the new layer count against this
73 limit. To retroactively compute Bloom filters over earlier layers, it is
74 advised to use `--split=replace`. Overrides the `commitGraph.maxNewFilters`
77 With the `--split[=<strategy>]` option, write the commit-graph as a
78 chain of multiple commit-graph files stored in
79 `<dir>/info/commit-graphs`. Commit-graph layers are merged based on the
80 strategy and other splitting options. The new commits not already in the
81 commit-graph are added in a new "tip" file. This file is merged with the
82 existing file if the following merge conditions are met:
84 * If `--split=no-merge` is specified, a merge is never performed, and
85 the remaining options are ignored. `--split=replace` overwrites the
86 existing chain with a new one. A bare `--split` defers to the remaining
87 options. (Note that merging a chain of commit graphs replaces the
88 existing chain with a length-1 chain where the first and only
89 incremental holds the entire graph).
91 * If `--size-multiple=<X>` is not specified, let `X` equal 2. If the new
92 tip file would have `N` commits and the previous tip has `M` commits and
93 `X` times `N` is greater than `M`, instead merge the two files into a
96 * If `--max-commits=<M>` is specified with `M` a positive integer, and the
97 new tip file would have more than `M` commits, then instead merge the new
98 tip with the previous tip.
100 Finally, if `--expire-time=<datetime>` is not specified, let `datetime`
101 be the current time. After writing the split commit-graph, delete all
102 unused commit-graph whose modified times are older than `datetime`.
106 Read the commit-graph file and verify its contents against the object
107 database. Used to check for corrupted data.
109 With the `--shallow` option, only check the tip commit-graph file in
110 a chain of split commit-graphs.
116 * Write a commit-graph file for the packed commits in your local `.git`
119 ------------------------------------------------
120 $ git commit-graph write
121 ------------------------------------------------
123 * Write a commit-graph file, extending the current commit-graph file
124 using commits in `<pack-index>`.
126 ------------------------------------------------
127 $ echo <pack-index> | git commit-graph write --stdin-packs
128 ------------------------------------------------
130 * Write a commit-graph file containing all reachable commits.
132 ------------------------------------------------
133 $ git show-ref -s | git commit-graph write --stdin-commits
134 ------------------------------------------------
136 * Write a commit-graph file containing all commits in the current
137 commit-graph file along with those reachable from `HEAD`.
139 ------------------------------------------------
140 $ git rev-parse HEAD | git commit-graph write --stdin-commits --append
141 ------------------------------------------------
146 Part of the linkgit:git[1] suite