Update paste-gpg-key-id.md

[dustinkirkland]

The documentation in here definitively does not work -- adding a trailing exclamation mark on a subkey causes git signing to fail:

$ GIT_TRACE=1 git commit -S -a
14:39:24.442514 git.c:455               trace: built-in: git commit -S -a
hint: Waiting for your editor to close the file... 14:39:24.461555 run-command.c:668       trace: run_command: GIT_INDEX_FILE=foo/.git/COMMIT_EDITMSG
14:39:39.240473 run-command.c:668       trace: run_command: gpg --status-fd=2 -bsau 'AD962CEE23420C1C'\!''
error: gpg failed to sign the data
fatal: failed to write commit object

However, omitting the trailing "!" works perfectly....

$ git config --global user.signingkey "AD962CEE23420C1C"
$ GIT_TRACE=1 git commit -S -a
14:42:37.225614 git.c:455               trace: built-in: git commit -S -a
hint: Waiting for your editor to close the file... 14:42:37.242806 run-command.c:668       trace: run_command: GIT_INDEX_FILE=foo/.git/COMMIT_EDITMSG
14:42:48.298643 run-command.c:668       trace: run_command: gpg --status-fd=2 -bsau AD962CEE23420C1C
14:42:48.601145 run-command.c:668       trace: run_command: git maintenance run --auto --no-quiet
14:42:48.602894 git.c:455               trace: built-in: git maintenance run --auto --no-quiet
[Makefile c850bc3a] ensure that we have a packages directory before mounting it
 1 file changed, 1 insertion(+)

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md	fpt ghec ghes@ 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.13 3.12 3.11 3.10	from reusable

---

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

[nguyenalex836]

@dustinkirkland Thanks so much for opening a PR! I'll get this triaged for review ✨

[felicitymay]

Based on the official git documentation, it seems as if the ! suffix is not needed. See:

• Git - Signing Your Work
• Git - Git Configuration
• Git - git-config Documentation

However, it seems as if there are times where ! (or escaped \!) is required to force using a specific key. See:

• ! https://www.gnupg.org/documentation/manuals/gnupg/Specify-a-User-ID.html

  When using gpg an exclamation mark (!) may be appended to force using the specified primary or secondary key and not to try and calculate which primary or secondary key to use.

• !https://vitalii.kozlovskyi.dev/posts/gpg-hardware-key-and-git-signing/
• \! https://www.hjdskes.nl/blog/psa-github-gpg/

Consequently, I'm going to expand your change to add this as an option.

[felicitymay]

I'm not sure why the preview's failing - I've tried re-running the workflow, which didn't make any difference 😞

I'm going to update this branch from main which will trigger the preview from scratch 🤞🏻

[felicitymay]

@dustinkirkland - this has the change you suggested, but still allows people to discover the use of an !, should they need it.

Since you're based in the US and I'm in Europe, I'm going to leave this for you to take a look at the preview: Telling Git about your GPG key with the intention of merging it tomorrow unless you spot any errors or concerns.

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡