1GIT-MKTAG(1) Git Manual GIT-MKTAG(1)
2
3
4
6 git-mktag - Creates a tag object with extra validation
7
9 git mktag
10
12 --strict
13 By default mktag turns on the equivalent of git-fsck(1) --strict
14 mode. Use --no-strict to disable it.
15
17 Reads a tag contents on standard input and creates a tag object. The
18 output is the new tag’s <object> identifier.
19
20 This command is mostly equivalent to git-hash-object(1) invoked with -t
21 tag -w --stdin. I.e. both of these will create and write a tag found in
22 my-tag:
23
24 git mktag <my-tag
25 git hash-object -t tag -w --stdin <my-tag
26
27 The difference is that mktag will die before writing the tag if the tag
28 doesn’t pass a git-fsck(1) check.
29
30 The "fsck" check done mktag is stricter than what git-fsck(1) would run
31 by default in that all fsck.<msg-id> messages are promoted from
32 warnings to errors (so e.g. a missing "tagger" line is an error).
33
34 Extra headers in the object are also an error under mktag, but ignored
35 by git-fsck(1). This extra check can be turned off by setting the
36 appropriate fsck.<msg-id> varible:
37
38 git -c fsck.extraHeaderEntry=ignore mktag <my-tag-with-headers
39
41 A tag signature file, to be fed to this command’s standard input, has a
42 very simple fixed format: four lines of
43
44 object <hash>
45 type <typename>
46 tag <tagname>
47 tagger <tagger>
48
49 followed by some optional free-form message (some tags created by older
50 Git may not have tagger line). The message, when it exists, is
51 separated by a blank line from the header. The message part may contain
52 a signature that Git itself doesn’t care about, but that can be
53 verified with gpg.
54
56 Part of the git(1) suite
57
58
59
60Git 2.31.1 2021-03-26 GIT-MKTAG(1)