1GIT-COMMIT-GRAPH(1) Git Manual GIT-COMMIT-GRAPH(1)
2
6 git-commit-graph - Write and verify Git commit-graph files
7
9 git commit-graph read [--object-dir <dir>]
10 git commit-graph verify [--object-dir <dir>] [--shallow] [--[no-]progress]
11 git commit-graph write <options> [--object-dir <dir>] [--[no-]progress]
12
15 Manage the serialized commit-graph file.
16
18 --object-dir
19 Use given directory for the location of packfiles and commit-graph
20 file. This parameter exists to specify the location of an alternate
21 that only has the objects directory, not a full .git directory. The
22 commit-graph file is expected to be in the <dir>/info directory and
23 the packfiles are expected to be in <dir>/pack.
24 --[no-]progress
26 Turn progress on/off explicitly. If neither is specified, progress
27 is shown if standard error is connected to a terminal.
28
30 write
31 Write a commit-graph file based on the commits found in packfiles.
32 With the --stdin-packs option, generate the new commit graph by
34 walking objects only in the specified pack-indexes. (Cannot be
35 combined with --stdin-commits or --reachable.)
36 With the --stdin-commits option, generate the new commit graph by
38 walking commits starting at the commits specified in stdin as a
39 list of OIDs in hex, one OID per line. (Cannot be combined with
40 --stdin-packs or --reachable.)
41 With the --reachable option, generate the new commit graph by
43 walking commits starting at all refs. (Cannot be combined with
44 --stdin-commits or --stdin-packs.)
45 With the --append option, include all commits that are present in
47 the existing commit-graph file.
48 With the --split option, write the commit-graph as a chain of
50 multiple commit-graph files stored in <dir>/info/commit-graphs. The
51 new commits not already in the commit-graph are added in a new
52 "tip" file. This file is merged with the existing file if the
53 following merge conditions are met:
54 · If --size-multiple=<X> is not specified, let X equal 2. If the
56 new tip file would have N commits and the previous tip has M
57 commits and X times N is greater than M, instead merge the two
58 files into a single file.
59 · If --max-commits=<M> is specified with M a positive integer,
61 and the new tip file would have more than M commits, then
62 instead merge the new tip with the previous tip.
63 Finally, if --expire-time=<datetime> is not specified, let
65 datetime be the current time. After writing the split
66 commit-graph, delete all unused commit-graph whose modified
67 times are older than datetime.
68 read
70 Read the commit-graph file and output basic details about it. Used
71 for debugging purposes.
72 verify
74 Read the commit-graph file and verify its contents against the
75 object database. Used to check for corrupted data.
76 With the --shallow option, only check the tip commit-graph file in
78 a chain of split commit-graphs.
79
81 · Write a commit-graph file for the packed commits in your local .git
82 directory.
83 $ git commit-graph write
85 · Write a commit-graph file, extending the current commit-graph file
88 using commits in <pack-index>.
89 $ echo <pack-index> | git commit-graph write --stdin-packs
91 · Write a commit-graph file containing all reachable commits.
94 $ git show-ref -s | git commit-graph write --stdin-commits
96 · Write a commit-graph file containing all commits in the current
99 commit-graph file along with those reachable from HEAD.
100 $ git rev-parse HEAD | git commit-graph write --stdin-commits --append
102 · Read basic information from the commit-graph file.
105 $ git commit-graph read
107
110 Part of the git(1) suite
111Git 2.24.1 12/10/2019 GIT-COMMIT-GRAPH(1)