6 git-tag - Create, list, delete or verify a tag object signed with GPG
12 'git tag' [-a | -s | -u <keyid>] [-f] [-m <msg> | -F <file>]
13 <tagname> [<commit> | <object>]
14 'git tag' -d <tagname>...
15 'git tag' [-n[<num>]] -l [--contains <commit>] [--no-contains <commit>]
16 [--points-at <object>] [--column[=<options>] | --no-column]
17 [--create-reflog] [--sort=<key>] [--format=<format>]
18 [--[no-]merged [<commit>]] [<pattern>...]
19 'git tag' -v [--format=<format>] <tagname>...
24 Add a tag reference in `refs/tags/`, unless `-d/-l/-v` is given
25 to delete, list or verify tags.
27 Unless `-f` is given, the named tag must not yet exist.
29 If one of `-a`, `-s`, or `-u <keyid>` is passed, the command
30 creates a 'tag' object, and requires a tag message. Unless
31 `-m <msg>` or `-F <file>` is given, an editor is started for the user to type
34 If `-m <msg>` or `-F <file>` is given and `-a`, `-s`, and `-u <keyid>`
35 are absent, `-a` is implied.
37 Otherwise just a tag reference for the SHA-1 object name of the commit object is
38 created (i.e. a lightweight tag).
40 A GnuPG signed tag object will be created when `-s` or `-u
41 <keyid>` is used. When `-u <keyid>` is not used, the
42 committer identity for the current user is used to find the
43 GnuPG key for signing. The configuration variable `gpg.program`
44 is used to specify custom GnuPG binary.
46 Tag objects (created with `-a`, `-s`, or `-u`) are called "annotated"
47 tags; they contain a creation date, the tagger name and e-mail, a
48 tagging message, and an optional GnuPG signature. Whereas a
49 "lightweight" tag is simply a name for an object (usually a commit
52 Annotated tags are meant for release while lightweight tags are meant
53 for private or temporary object labels. For this reason, some git
54 commands for naming objects (like `git describe`) will ignore
55 lightweight tags by default.
62 Make an unsigned, annotated tag object
66 Make a GPG-signed tag, using the default e-mail address's key.
69 --local-user=<keyid>::
70 Make a GPG-signed tag, using the given key.
74 Replace an existing tag with the given name (instead of failing)
78 Delete existing tags with the given names.
82 Verify the GPG signature of the given tag names.
85 <num> specifies how many lines from the annotation, if any,
86 are printed when using -l. Implies `--list`.
88 The default is not to print any annotation lines.
89 If no number is given to `-n`, only the first line is printed.
90 If the tag is not annotated, the commit message is displayed instead.
94 List tags. With optional `<pattern>...`, e.g. `git tag --list
95 'v-*'`, list only the tags that match the pattern(s).
97 Running "git tag" without arguments also lists all tags. The pattern
98 is a shell wildcard (i.e., matched using fnmatch(3)). Multiple
99 patterns may be given; if any of them matches, the tag is shown.
101 This option is implicitly supplied if any other list-like option such
102 as `--contains` is provided. See the documentation for each of those
106 Sort based on the key given. Prefix `-` to sort in
107 descending order of the value. You may use the --sort=<key> option
108 multiple times, in which case the last key becomes the primary
109 key. Also supports "version:refname" or "v:refname" (tag
110 names are treated as versions). The "version:refname" sort
111 order can also be affected by the "versionsort.suffix"
112 configuration variable.
113 The keys supported are the same as those in `git for-each-ref`.
114 Sort order defaults to the value configured for the `tag.sort`
115 variable if it exists, or lexicographic order otherwise. See
116 linkgit:git-config[1].
119 Respect any colors specified in the `--format` option. The
120 `<when>` field must be one of `always`, `never`, or `auto` (if
121 `<when>` is absent, behave as if `always` was given).
125 Sorting and filtering tags are case insensitive.
127 --column[=<options>]::
129 Display tag listing in columns. See configuration variable
130 column.tag for option syntax.`--column` and `--no-column`
131 without options are equivalent to 'always' and 'never' respectively.
133 This option is only applicable when listing tags without annotation lines.
135 --contains [<commit>]::
136 Only list tags which contain the specified commit (HEAD if not
137 specified). Implies `--list`.
139 --no-contains [<commit>]::
140 Only list tags which don't contain the specified commit (HEAD if
141 not specified). Implies `--list`.
143 --merged [<commit>]::
144 Only list tags whose commits are reachable from the specified
145 commit (`HEAD` if not specified), incompatible with `--no-merged`.
147 --no-merged [<commit>]::
148 Only list tags whose commits are not reachable from the specified
149 commit (`HEAD` if not specified), incompatible with `--merged`.
151 --points-at <object>::
152 Only list tags of the given object (HEAD if not
153 specified). Implies `--list`.
157 Use the given tag message (instead of prompting).
158 If multiple `-m` options are given, their values are
159 concatenated as separate paragraphs.
160 Implies `-a` if none of `-a`, `-s`, or `-u <keyid>`
165 Take the tag message from the given file. Use '-' to
166 read the message from the standard input.
167 Implies `-a` if none of `-a`, `-s`, or `-u <keyid>`
171 This option sets how the tag message is cleaned up.
172 The '<mode>' can be one of 'verbatim', 'whitespace' and 'strip'. The
173 'strip' mode is default. The 'verbatim' mode does not change message at
174 all, 'whitespace' removes just leading/trailing whitespace lines and
175 'strip' removes both whitespace and commentary.
178 Create a reflog for the tag. To globally enable reflogs for tags, see
179 `core.logAllRefUpdates` in linkgit:git-config[1].
180 The negated form `--no-create-reflog` only overrides an earlier
181 `--create-reflog`, but currently does not negate the setting of
182 `core.logAllRefUpdates`.
185 The name of the tag to create, delete, or describe.
186 The new tag name must pass all checks defined by
187 linkgit:git-check-ref-format[1]. Some of these checks
188 may restrict the characters allowed in a tag name.
192 The object that the new tag will refer to, usually a commit.
196 A string that interpolates `%(fieldname)` from a tag ref being shown
197 and the object it points at. The format is the same as
198 that of linkgit:git-for-each-ref[1]. When unspecified,
199 defaults to `%(refname:strip=2)`.
203 By default, 'git tag' in sign-with-default mode (-s) will use your
204 committer identity (of the form `Your Name <your@email.address>`) to
205 find a key. If you want to use a different default key, you can specify
206 it in the repository configuration as follows:
208 -------------------------------------
210 signingKey = <gpg-keyid>
211 -------------------------------------
213 `pager.tag` is only respected when listing tags, i.e., when `-l` is
214 used or implied. The default is to use a pager.
215 See linkgit:git-config[1].
223 What should you do when you tag a wrong commit and you would
226 If you never pushed anything out, just re-tag it. Use "-f" to
227 replace the old one. And you're done.
229 But if you have pushed things out (or others could just read
230 your repository directly), then others will have already seen
231 the old tag. In that case you can do one of two things:
234 Just admit you screwed up, and use a different name. Others have
235 already seen one tag-name, and if you keep the same name, you
236 may be in the situation that two people both have "version X",
237 but they actually have 'different' "X"'s. So just call it "X.1"
241 You really want to call the new version "X" too, 'even though'
242 others have already seen the old one. So just use 'git tag -f'
243 again, as if you hadn't already published the old one.
245 However, Git does *not* (and it should not) change tags behind
246 users back. So if somebody already got the old tag, doing a
247 'git pull' on your tree shouldn't just make them overwrite the old
250 If somebody got a release tag from you, you cannot just change
251 the tag for them by updating your own one. This is a big
252 security issue, in that people MUST be able to trust their
253 tag-names. If you really want to do the insane thing, you need
254 to just fess up to it, and tell people that you messed up. You
255 can do that by making a very public announcement saying:
258 Ok, I messed up, and I pushed out an earlier version tagged as X. I
259 then fixed something, and retagged the *fixed* tree as X again.
261 If you got the wrong tag, and want the new one, please delete
262 the old one and fetch the new one by doing:
265 git fetch origin tag X
267 to get my updated tag.
269 You can test which tag you have by doing
273 which should return 0123456789abcdef.. if you have the new version.
275 Sorry for the inconvenience.
278 Does this seem a bit complicated? It *should* be. There is no
279 way that it would be correct to just "fix" it automatically.
280 People need to know that their tags might have been changed.
283 On Automatic following
284 ~~~~~~~~~~~~~~~~~~~~~~
286 If you are following somebody else's tree, you are most likely
287 using remote-tracking branches (eg. `refs/remotes/origin/master`).
288 You usually want the tags from the other end.
290 On the other hand, if you are fetching because you would want a
291 one-shot merge from somebody else, you typically do not want to
292 get tags from there. This happens more often for people near
293 the toplevel but not limited to them. Mere mortals when pulling
294 from each other do not necessarily want to automatically get
295 private anchor point tags from the other person.
297 Often, "please pull" messages on the mailing list just provide
298 two pieces of information: a repo URL and a branch name; this
299 is designed to be easily cut&pasted at the end of a 'git fetch'
303 Linus, please pull from
305 git://git..../proj.git master
307 to get the following updates...
313 $ git pull git://git..../proj.git master
316 In such a case, you do not want to automatically follow the other
319 One important aspect of Git is its distributed nature, which
320 largely means there is no inherent "upstream" or
321 "downstream" in the system. On the face of it, the above
322 example might seem to indicate that the tag namespace is owned
323 by the upper echelon of people and that tags only flow downwards, but
324 that is not the case. It only shows that the usage pattern
325 determines who are interested in whose tags.
327 A one-shot pull is a sign that a commit history is now crossing
328 the boundary between one circle of people (e.g. "people who are
329 primarily interested in the networking part of the kernel") who may
330 have their own set of tags (e.g. "this is the third release
331 candidate from the networking group to be proposed for general
332 consumption with 2.6.21 release") to another circle of people
333 (e.g. "people who integrate various subsystem improvements").
334 The latter are usually not interested in the detailed tags used
335 internally in the former group (that is what "internal" means).
336 That is why it is desirable not to follow tags automatically in
339 It may well be that among networking people, they may want to
340 exchange the tags internal to their group, but in that workflow
341 they are most likely tracking each other's progress by
342 having remote-tracking branches. Again, the heuristic to automatically
343 follow such tags is a good thing.
349 If you have imported some changes from another VCS and would like
350 to add tags for major releases of your work, it is useful to be able
351 to specify the date to embed inside of the tag object; such data in
352 the tag object affects, for example, the ordering of tags in the
355 To set the date used in future tag objects, set the environment
356 variable GIT_COMMITTER_DATE (see the later discussion of possible
357 values; the most common form is "YYYY-MM-DD HH:MM").
362 $ GIT_COMMITTER_DATE="2006-10-02 10:31" git tag -s v1.0.1
365 include::date-formats.txt[]
369 linkgit:git-check-ref-format[1].
370 linkgit:git-config[1].
374 Part of the linkgit:git[1] suite
projects / git / blob