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