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 verify [--object-dir <dir>] [--shallow] [--[no-]progress]
10 git commit-graph write <options> [--object-dir <dir>] [--[no-]progress]
11
13 Manage the serialized commit-graph file.
14
16 --object-dir
17 Use given directory for the location of packfiles and commit-graph
18 file. This parameter exists to specify the location of an alternate
19 that only has the objects directory, not a full .git directory. The
20 commit-graph file is expected to be in the <dir>/info directory and
21 the packfiles are expected to be in <dir>/pack. If the directory
22 could not be made into an absolute path, or does not match any
23 known object directory, git commit-graph ... will exit with
24 non-zero status.
25 --[no-]progress
27 Turn progress on/off explicitly. If neither is specified, progress
28 is shown if standard error is connected to a terminal.
29
31 write
32 Write a commit-graph file based on the commits found in packfiles.
33 With the --stdin-packs option, generate the new commit graph by
35 walking objects only in the specified pack-indexes. (Cannot be
36 combined with --stdin-commits or --reachable.)
37 With the --stdin-commits option, generate the new commit graph by
39 walking commits starting at the commits specified in stdin as a
40 list of OIDs in hex, one OID per line. (Cannot be combined with
41 --stdin-packs or --reachable.)
42 With the --reachable option, generate the new commit graph by
44 walking commits starting at all refs. (Cannot be combined with
45 --stdin-commits or --stdin-packs.)
46 With the --append option, include all commits that are present in
48 the existing commit-graph file.
49 With the --split option, write the commit-graph as a chain of
51 multiple commit-graph files stored in <dir>/info/commit-graphs. The
52 new commits not already in the commit-graph are added in a new
53 "tip" file. This file is merged with the existing file if the
54 following merge conditions are met:
55 · If --size-multiple=<X> is not specified, let X equal 2. If the
57 new tip file would have N commits and the previous tip has M
58 commits and X times N is greater than M, instead merge the two
59 files into a single file.
60 · If --max-commits=<M> is specified with M a positive integer,
62 and the new tip file would have more than M commits, then
63 instead merge the new tip with the previous tip.
64 Finally, if --expire-time=<datetime> is not specified, let
66 datetime be the current time. After writing the split
67 commit-graph, delete all unused commit-graph whose modified
68 times are older than datetime.
69 verify
71 Read the commit-graph file and verify its contents against the
72 object database. Used to check for corrupted data.
73 With the --shallow option, only check the tip commit-graph file in
75 a chain of split commit-graphs.
76
78 · Write a commit-graph file for the packed commits in your local .git
79 directory.
80 $ git commit-graph write
82 · Write a commit-graph file, extending the current commit-graph file
84 using commits in <pack-index>.
85 $ echo <pack-index> | git commit-graph write --stdin-packs
87 · Write a commit-graph file containing all reachable commits.
89 $ git show-ref -s | git commit-graph write --stdin-commits
91 · Write a commit-graph file containing all commits in the current
93 commit-graph file along with those reachable from HEAD.
94 $ git rev-parse HEAD | git commit-graph write --stdin-commits --append
96
98 Part of the git(1) suite
99Git 2.26.2 2020-04-20 GIT-COMMIT-GRAPH(1)