Git fork
1`badDate`::
2 (ERROR) Invalid date format in an author/committer line.
3
4`badDateOverflow`::
5 (ERROR) Invalid date value in an author/committer line.
6
7`badEmail`::
8 (ERROR) Invalid email format in an author/committer line.
9
10`badFilemode`::
11 (INFO) A tree contains a bad filemode entry.
12
13`badGpgsig`::
14 (ERROR) A tag contains a bad (truncated) signature (e.g., `gpgsig`) header.
15
16`badHeaderContinuation`::
17 (ERROR) A continuation header (such as for `gpgsig`) is unexpectedly truncated.
18
19`badName`::
20 (ERROR) An author/committer name is empty.
21
22`badObjectSha1`::
23 (ERROR) An object has a bad sha1.
24
25`badPackedRefEntry`::
26 (ERROR) The "packed-refs" file contains an invalid entry.
27
28`badPackedRefHeader`::
29 (ERROR) The "packed-refs" file contains an invalid
30 header.
31
32`badParentSha1`::
33 (ERROR) A commit object has a bad parent sha1.
34
35`badRefContent`::
36 (ERROR) A ref has bad content.
37
38`badRefFiletype`::
39 (ERROR) A ref has a bad file type.
40
41`badRefName`::
42 (ERROR) A ref has an invalid format.
43
44`badReferentName`::
45 (ERROR) The referent name of a symref is invalid.
46
47`badReftableTableName`::
48 (WARN) A reftable table has an invalid name.
49
50`badTagName`::
51 (INFO) A tag has an invalid format.
52
53`badTimezone`::
54 (ERROR) Found an invalid time zone in an author/committer line.
55
56`badTree`::
57 (ERROR) A tree cannot be parsed.
58
59`badTreeSha1`::
60 (ERROR) A tree has an invalid format.
61
62`badType`::
63 (ERROR) Found an invalid object type.
64
65`duplicateEntries`::
66 (ERROR) A tree contains duplicate file entries.
67
68`emptyName`::
69 (WARN) A path contains an empty name.
70
71`emptyPackedRefsFile`::
72 (INFO) "packed-refs" file is empty. Report to the
73 git@vger.kernel.org mailing list if you see this error. As only
74 very early versions of Git would create such an empty
75 "packed_refs" file, we might tighten this rule in the future.
76
77`extraHeaderEntry`::
78 (IGNORE) Extra headers found after `tagger`.
79
80`fullPathname`::
81 (WARN) A path contains the full path starting with "/".
82
83`gitattributesBlob`::
84 (ERROR) A non-blob found at `.gitattributes`.
85
86`gitattributesLarge`::
87 (ERROR) The `.gitattributes` blob is too large.
88
89`gitattributesLineLength`::
90 (ERROR) The `.gitattributes` blob contains too long lines.
91
92`gitattributesMissing`::
93 (ERROR) Unable to read `.gitattributes` blob.
94
95`gitattributesSymlink`::
96 (INFO) `.gitattributes` is a symlink.
97
98`gitignoreSymlink`::
99 (INFO) `.gitignore` is a symlink.
100
101`gitmodulesBlob`::
102 (ERROR) A non-blob found at `.gitmodules`.
103
104`gitmodulesLarge`::
105 (ERROR) The `.gitmodules` file is too large to parse.
106
107`gitmodulesMissing`::
108 (ERROR) Unable to read `.gitmodules` blob.
109
110`gitmodulesName`::
111 (ERROR) A submodule name is invalid.
112
113`gitmodulesParse`::
114 (INFO) Could not parse `.gitmodules` blob.
115
116`gitmodulesPath`::
117 (ERROR) `.gitmodules` path is invalid.
118
119`gitmodulesSymlink`::
120 (ERROR) `.gitmodules` is a symlink.
121
122`gitmodulesUpdate`::
123 (ERROR) Found an invalid submodule update setting.
124
125`gitmodulesUrl`::
126 (ERROR) Found an invalid submodule url.
127
128`hasDot`::
129 (WARN) A tree contains an entry named `.`.
130
131`hasDotdot`::
132 (WARN) A tree contains an entry named `..`.
133
134`hasDotgit`::
135 (WARN) A tree contains an entry named `.git`.
136
137`largePathname`::
138 (WARN) A tree contains an entry with a very long path name. If
139 the value of `fsck.largePathname` contains a colon, that value
140 is used as the maximum allowable length (e.g., "warn:10" would
141 complain about any path component of 11 or more bytes). The
142 default value is 4096.
143
144`mailmapSymlink`::
145 (INFO) `.mailmap` is a symlink.
146
147`missingAuthor`::
148 (ERROR) Author is missing.
149
150`missingCommitter`::
151 (ERROR) Committer is missing.
152
153`missingEmail`::
154 (ERROR) Email is missing in an author/committer line.
155
156`missingNameBeforeEmail`::
157 (ERROR) Missing name before an email in an author/committer line.
158
159`missingObject`::
160 (ERROR) Missing `object` line in tag object.
161
162`missingSpaceBeforeDate`::
163 (ERROR) Missing space before date in an author/committer line.
164
165`missingSpaceBeforeEmail`::
166 (ERROR) Missing space before the email in an author/committer line.
167
168`missingTag`::
169 (ERROR) Unexpected end after `type` line in a tag object.
170
171`missingTagEntry`::
172 (ERROR) Missing `tag` line in a tag object.
173
174`missingTaggerEntry`::
175 (INFO) Missing `tagger` line in a tag object.
176
177`missingTree`::
178 (ERROR) Missing `tree` line in a commit object.
179
180`missingType`::
181 (ERROR) Invalid type value on the `type` line in a tag object.
182
183`missingTypeEntry`::
184 (ERROR) Missing `type` line in a tag object.
185
186`multipleAuthors`::
187 (ERROR) Multiple author lines found in a commit.
188
189`nulInCommit`::
190 (WARN) Found a NUL byte in the commit object body.
191
192`nulInHeader`::
193 (FATAL) NUL byte exists in the object header.
194
195`nullSha1`::
196 (WARN) Tree contains entries pointing to a null sha1.
197
198`packedRefEntryNotTerminated`::
199 (ERROR) The "packed-refs" file contains an entry that is
200 not terminated by a newline.
201
202`packedRefUnsorted`::
203 (ERROR) The "packed-refs" file is not sorted.
204
205`refMissingNewline`::
206 (INFO) A loose ref that does not end with newline(LF). As
207 valid implementations of Git never created such a loose ref
208 file, it may become an error in the future. Report to the
209 git@vger.kernel.org mailing list if you see this error, as
210 we need to know what tools created such a file.
211
212`symlinkRef`::
213 (INFO) A symbolic link is used as a symref. Report to the
214 git@vger.kernel.org mailing list if you see this error, as we
215 are assessing the feasibility of dropping the support to drop
216 creating symbolic links as symrefs.
217
218`symrefTargetIsNotARef`::
219 (INFO) The target of a symbolic reference points neither to
220 a root reference nor to a reference starting with "refs/".
221 Although we allow create a symref pointing to the referent which
222 is outside the "ref" by using `git symbolic-ref`, we may tighten
223 the rule in the future. Report to the git@vger.kernel.org
224 mailing list if you see this error, as we need to know what tools
225 created such a file.
226
227`trailingRefContent`::
228 (INFO) A loose ref has trailing content. As valid implementations
229 of Git never created such a loose ref file, it may become an
230 error in the future. Report to the git@vger.kernel.org mailing
231 list if you see this error, as we need to know what tools
232 created such a file.
233
234`treeNotSorted`::
235 (ERROR) A tree is not properly sorted.
236
237`unknownType`::
238 (ERROR) Found an unknown object type.
239
240`unterminatedHeader`::
241 (FATAL) Missing end-of-line in the object header.
242
243`zeroPaddedDate`::
244 (ERROR) Found a zero padded date in an author/committer line.
245
246`zeroPaddedFilemode`::
247 (WARN) Found a zero padded filemode in a tree.