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. (Cannot be combined with
51 `--stdin-packs` or `--reachable`.)
53 With the `--reachable` option, generate the new commit graph by walking
54 commits starting at all refs. (Cannot be combined with `--stdin-commits`
57 With the `--append` option, include all commits that are present in the
58 existing commit-graph file.
60 With the `--changed-paths` option, compute and write information about the
61 paths changed between a commit and it's first parent. This operation can
62 take a while on large repositories. It provides significant performance gains
63 for getting history of a directory or a file with `git log -- <path>`.
65 With the `--split` option, write the commit-graph as a chain of multiple
66 commit-graph files stored in `<dir>/info/commit-graphs`. The new commits
67 not already in the commit-graph are added in a new "tip" file. This file
68 is merged with the existing file if the following merge conditions are
71 * If `--size-multiple=<X>` is not specified, let `X` equal 2. If the new
72 tip file would have `N` commits and the previous tip has `M` commits and
73 `X` times `N` is greater than `M`, instead merge the two files into a
76 * If `--max-commits=<M>` is specified with `M` a positive integer, and the
77 new tip file would have more than `M` commits, then instead merge the new
78 tip with the previous tip.
80 Finally, if `--expire-time=<datetime>` is not specified, let `datetime`
81 be the current time. After writing the split commit-graph, delete all
82 unused commit-graph whose modified times are older than `datetime`.
86 Read the commit-graph file and verify its contents against the object
87 database. Used to check for corrupted data.
89 With the `--shallow` option, only check the tip commit-graph file in
90 a chain of split commit-graphs.
96 * Write a commit-graph file for the packed commits in your local `.git`
99 ------------------------------------------------
100 $ git commit-graph write
101 ------------------------------------------------
103 * Write a commit-graph file, extending the current commit-graph file
104 using commits in `<pack-index>`.
106 ------------------------------------------------
107 $ echo <pack-index> | git commit-graph write --stdin-packs
108 ------------------------------------------------
110 * Write a commit-graph file containing all reachable commits.
112 ------------------------------------------------
113 $ git show-ref -s | git commit-graph write --stdin-commits
114 ------------------------------------------------
116 * Write a commit-graph file containing all commits in the current
117 commit-graph file along with those reachable from `HEAD`.
119 ------------------------------------------------
120 $ git rev-parse HEAD | git commit-graph write --stdin-commits --append
121 ------------------------------------------------
126 Part of the linkgit:git[1] suite