@@ -3,7 +3,7 @@ git-tag(1)
33
44NAME
55----
6- git-tag - Create, list, delete or verify a tag object signed with GPG
6+ git-tag - Create, list, delete or verify tags
77
88
99SYNOPSIS
@@ -38,15 +38,17 @@ and `-a`, `-s`, and `-u <key-id>` are absent, `-a` is implied.
3838Otherwise, a tag reference that points directly at the given object
3939(i.e., a lightweight tag) is created.
4040
41- A GnuPG signed tag object will be created when `-s` or `-u
42- <key-id >` is used. When ` -u <key-id >` is not used, the
43- committer identity for the current user is used to find the
44- GnuPG key for signing. The configuration variable `gpg.program`
45- is used to specify custom GnuPG binary.
41+ A cryptographically signed tag object will be created when `-s` or
42+ `-u <key-id>` is used. The signing backend (GPG, X.509, SSH, etc.) is
43+ controlled by the `gpg.format` configuration variable, defaulting to
44+ OpenPGP. When `-u <key-id>` is not used, the committer identity for
45+ the current user is used to find the key for signing. The
46+ configuration variable `gpg.program` is used to specify a custom
47+ signing binary.
4648
4749Tag objects (created with `-a` , `-s` , or `-u` ) are called "annotated"
4850tags; they contain a creation date, the tagger name and e-mail, a
49- tagging message, and an optional GnuPG signature. Whereas a
51+ tagging message, and an optional cryptographic signature. Whereas a
5052"lightweight" tag is simply a name for an object (usually a commit
5153object).
5254
@@ -64,18 +66,23 @@ OPTIONS
6466
6567`-s` ::
6668`--sign` ::
67- Make a GPG-signed tag, using the default e-mail address's key.
68- The default behavior of tag GPG-signing is controlled by `tag.gpgSign`
69- configuration variable if it exists, or disabled otherwise.
70- See linkgit:git-config[1].
69+ Make a cryptographically signed tag, using the default signing
70+ key. The signing backend used depends on the `gpg.format`
71+ configuration variable. The default key is determined by the
72+ backend. For GPG, it's based on the committer's email address,
73+ while for SSH it may be a specific key file or agent
74+ identity. See linkgit:git-config[1].
7175
7276`--no-sign` ::
7377 Override `tag.gpgSign` configuration variable that is
7478 set to force each and every tag to be signed.
7579
7680`-u <key-id>` ::
7781`--local-user=<key-id>` ::
78- Make a GPG-signed tag, using the given key.
82+ Make a cryptographically signed tag using the given key. The
83+ format of the <key-id > and the backend used depend on the
84+ `gpg.format` configuration variable. See
85+ linkgit:git-config[1].
7986
8087`-f` ::
8188`--force` ::
@@ -87,7 +94,7 @@ OPTIONS
8794
8895`-v` ::
8996`--verify` ::
90- Verify the GPG signature of the given tag names .
97+ Verify the cryptographic signature of the given tags .
9198
9299`-n<num>` ::
93100 _<num>_ specifies how many lines from the annotation, if any,
@@ -235,12 +242,23 @@ it in the repository configuration as follows:
235242
236243-------------------------------------
237244[user]
238- signingKey = <gpg- key-id>
245+ signingKey = <key-id>
239246-------------------------------------
240247
248+ The signing backend can be chosen via the `gpg.format` configuration
249+ variable, which defaults to `openpgp` . See linkgit:git-config[1]
250+ for a list of other supported formats.
251+
252+ The path to the program used for each signing backend can be specified
253+ with the `gpg.<format>.program` configuration variable. For the
254+ `openpgp` backend, `gpg.program` can be used as a synonym for
255+ `gpg.openpgp.program` . See linkgit:git-config[1] for details.
256+
241257`pager.tag` is only respected when listing tags, i.e., when `-l` is
242258used or implied. The default is to use a pager.
243- See linkgit:git-config[1].
259+
260+ See linkgit:git-config[1] for more details and other configuration
261+ variables.
244262
245263DISCUSSION
246264----------
0 commit comments