table of contents
other versions
- wheezy 1:1.7.10.4-1+wheezy3
- wheezy-backports 1:1.9.1-1~bpo70+2
- jessie 1:2.1.4-2.1+deb8u2
- jessie-backports 1:2.11.0-3~bpo8+1
- testing 1:2.11.0-3
- unstable 1:2.11.0-4
- experimental 1:2.13.1+next.20170610-1
GIT-TAG(1) | Git Manual | GIT-TAG(1) |
NAME¶
git-tag - Create, list, delete or verify a tag object signed with GPGSYNOPSIS¶
git tag [-a | -s | -u <key-id>] [-f] [-m <msg> | -F <file>] <tagname> [<commit> | <object>] git tag -d <tagname>... git tag [-n[<num>]] -l [--contains <commit>] [--points-at <object>] [<pattern>...] git tag -v <tagname>...
DESCRIPTION¶
Add a tag reference in .git/refs/tags/, unless -d/-l/-v is given to delete, list or verify tags.OPTIONS¶
-a, --annotateMake an unsigned, annotated tag object
-s, --sign
Make a GPG-signed tag, using the default
e-mail address’s key.
-u <key-id>, --local-user=<key-id>
Make a GPG-signed tag, using the given
key.
-f, --force
Replace an existing tag with the given name
(instead of failing)
-d, --delete
Delete existing tags with the given
names.
-v, --verify
Verify the gpg signature of the given tag
names.
-n<num>
<num> specifies how many lines from the
annotation, if any, are printed when using -l. The default is not to print any
annotation lines. If no number is given to -n, only the first line is printed.
If the tag is not annotated, the commit message is displayed instead.
-l <pattern>, --list <pattern>
List tags with names that match the given
pattern (or all if no pattern is given). Running "git tag" without
arguments also lists all tags. The pattern is a shell wildcard (i.e., matched
using fnmatch(3)). Multiple patterns may be given; if any of them matches, the
tag is shown.
--contains <commit>
Only list tags which contain the specified
commit.
--points-at <object>
Only list tags of the given object.
-m <msg>, --message=<msg>
Use the given tag message (instead of
prompting). If multiple -m options are given, their values are concatenated as
separate paragraphs. Implies -a if none of -a, -s, or -u <key-id> is
given.
-F <file>, --file=<file>
Take the tag message from the given file. Use
- to read the message from the standard input. Implies -a if none of
-a, -s, or -u <key-id> is given.
--cleanup=<mode>
This option sets how the tag message is
cleaned up. The <mode> can be one of verbatim,
whitespace and strip. The strip mode is default. The
verbatim mode does not change message at all, whitespace removes
just leading/trailing whitespace lines and strip removes both
whitespace and commentary.
<tagname>
The name of the tag to create, delete, or
describe. The new tag name must pass all checks defined by
git-check-ref-format(1). Some of these checks may restrict the
characters allowed in a tag name.
CONFIGURATION¶
By default, git tag in sign-with-default mode (-s) will use your committer identity (of the form "Your Name < your@email.address[1]>") to find a key. If you want to use a different default key, you can specify it in the repository configuration as follows:[user] signingkey = <gpg-key-id>
DISCUSSION¶
On Re-tagging¶
What should you do when you tag a wrong commit and you would want to re-tag? 1.The sane thing. Just admit you screwed up,
and use a different name. Others have already seen one tag-name, and if you
keep the same name, you may be in the situation that two people both have
"version X", but they actually have different
"X"'s. So just call it "X.1" and be done with it.
2.The insane thing. You really want to call
the new version "X" too, even though others have already seen
the old one. So just use git tag -f again, as if you hadn’t
already published the old one.
Ok, I messed up, and I pushed out an earlier version tagged as X. I then fixed something, and retagged the *fixed* tree as X again. If you got the wrong tag, and want the new one, please delete the old one and fetch the new one by doing: git tag -d X git fetch origin tag X to get my updated tag. You can test which tag you have by doing git rev-parse X which should return 0123456789abcdef.. if you have the new version. Sorry for the inconvenience.
On Automatic following¶
If you are following somebody else’s tree, you are most likely using remote-tracking branches (refs/heads/origin in traditional layout, or refs/remotes/origin/master in the separate-remote layout). You usually want the tags from the other end.Linus, please pull from git://git..../proj.git master to get the following updates...
$ git pull git://git..../proj.git master
On Backdating Tags¶
If you have imported some changes from another VCS and would like to add tags for major releases of your work, it is useful to be able to specify the date to embed inside of the tag object; such data in the tag object affects, for example, the ordering of tags in the gitweb interface.$ GIT_COMMITTER_DATE="2006-10-02 10:31" git tag -s v1.0.1
DATE FORMATS¶
The GIT_AUTHOR_DATE, GIT_COMMITTER_DATE environment variables support the following date formats: Git internal formatIt is <unix timestamp> <timezone
offset>, where <unix timestamp> is the number of seconds since the
UNIX epoch. <timezone offset> is a positive or negative offset from UTC.
For example CET (which is 2 hours ahead UTC) is +0200.
RFC 2822
The standard email format as described by RFC
2822, for example Thu, 07 Apr 2005 22:13:13 +0200.
ISO 8601
Time and date specified by the ISO 8601
standard, for example 2005-04-07T22:13:13. The parser accepts a space instead
of the T character as well.
Note
In addition, the date part is accepted in the following formats: YYYY.MM.DD,
MM/DD/YYYY and DD.MM.YYYY.
SEE ALSO¶
git-check-ref-format(1).GIT¶
Part of the git(1) suiteNOTES¶
- 1.
- your@email.address
mailto:your@email.address
03/19/2016 | Git 1.7.10.4 |