1GIT-COMMIT-GRAPH(1)               Git Manual               GIT-COMMIT-GRAPH(1)
2
3
4

NAME

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

SYNOPSIS

9       git commit-graph verify [--object-dir <dir>] [--shallow] [--[no-]progress]
10       git commit-graph write <options> [--object-dir <dir>] [--[no-]progress]
11

DESCRIPTION

13       Manage the serialized commit-graph file.
14

OPTIONS

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
26       --[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

COMMANDS

31       write
32           Write a commit-graph file based on the commits found in packfiles.
33           If the config option core.commitGraph is disabled, then this
34           command will output a warning, then return success without writing
35           a commit-graph file.
36
37           With the --stdin-packs option, generate the new commit graph by
38           walking objects only in the specified pack-indexes. (Cannot be
39           combined with --stdin-commits or --reachable.)
40
41           With the --stdin-commits option, generate the new commit graph by
42           walking commits starting at the commits specified in stdin as a
43           list of OIDs in hex, one OID per line. OIDs that resolve to
44           non-commits (either directly, or by peeling tags) are silently
45           ignored. OIDs that are malformed, or do not exist generate an
46           error. (Cannot be combined with --stdin-packs or --reachable.)
47
48           With the --reachable option, generate the new commit graph by
49           walking commits starting at all refs. (Cannot be combined with
50           --stdin-commits or --stdin-packs.)
51
52           With the --append option, include all commits that are present in
53           the existing commit-graph file.
54
55           With the --changed-paths option, compute and write information
56           about the paths changed between a commit and its first parent. This
57           operation can take a while on large repositories. It provides
58           significant performance gains for getting history of a directory or
59           a file with git log -- <path>. If this option is given, future
60           commit-graph writes will automatically assume that this option was
61           intended. Use --no-changed-paths to stop storing this data.
62
63           With the --max-new-filters=<n> option, generate at most n new Bloom
64           filters (if --changed-paths is specified). If n is -1, no limit is
65           enforced. Only commits present in the new layer count against this
66           limit. To retroactively compute Bloom filters over earlier layers,
67           it is advised to use --split=replace. Overrides the
68           commitGraph.maxNewFilters configuration.
69
70           With the --split[=<strategy>] option, write the commit-graph as a
71           chain of multiple commit-graph files stored in
72           <dir>/info/commit-graphs. Commit-graph layers are merged based on
73           the strategy and other splitting options. The new commits not
74           already in the commit-graph are added in a new "tip" file. This
75           file is merged with the existing file if the following merge
76           conditions are met:
77
78           •   If --split=no-merge is specified, a merge is never performed,
79               and the remaining options are ignored.  --split=replace
80               overwrites the existing chain with a new one. A bare --split
81               defers to the remaining options. (Note that merging a chain of
82               commit graphs replaces the existing chain with a length-1 chain
83               where the first and only incremental holds the entire graph).
84
85           •   If --size-multiple=<X> is not specified, let X equal 2. If the
86               new tip file would have N commits and the previous tip has M
87               commits and X times N is greater than M, instead merge the two
88               files into a single file.
89
90           •   If --max-commits=<M> is specified with M a positive integer,
91               and the new tip file would have more than M commits, then
92               instead merge the new tip with the previous tip.
93
94               Finally, if --expire-time=<datetime> is not specified, let
95               datetime be the current time. After writing the split
96               commit-graph, delete all unused commit-graph whose modified
97               times are older than datetime.
98
99       verify
100           Read the commit-graph file and verify its contents against the
101           object database. Used to check for corrupted data.
102
103           With the --shallow option, only check the tip commit-graph file in
104           a chain of split commit-graphs.
105

EXAMPLES

107       •   Write a commit-graph file for the packed commits in your local .git
108           directory.
109
110               $ git commit-graph write
111
112       •   Write a commit-graph file, extending the current commit-graph file
113           using commits in <pack-index>.
114
115               $ echo <pack-index> | git commit-graph write --stdin-packs
116
117       •   Write a commit-graph file containing all reachable commits.
118
119               $ git show-ref -s | git commit-graph write --stdin-commits
120
121       •   Write a commit-graph file containing all commits in the current
122           commit-graph file along with those reachable from HEAD.
123
124               $ git rev-parse HEAD | git commit-graph write --stdin-commits --append
125

GIT

127       Part of the git(1) suite
128
129
130
131Git 2.36.1                        2022-05-05               GIT-COMMIT-GRAPH(1)
Impressum