8f964ea2cb
Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> Co-authored-by: Grace Park <gracepark@github.com> Co-authored-by: Steve Guntrip <12534592+stevecat@users.noreply.github.com> Co-authored-by: Robert Sese <sese@github.com> Co-authored-by: Peter Bengtsson <peterbe@github.com> Co-authored-by: Rachael Sewell <rachmari@github.com>
1.7 KiB
1.7 KiB
title, intro, redirect_from, versions, topics, shortTitle
| title | intro | redirect_from | versions | topics | shortTitle | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Checking for existing GPG keys | Before you generate a GPG key, you can check to see if you have any existing GPG keys. |
|
|
|
Existing GPG keys |
{% data reusables.gpg.supported-gpg-key-algorithms %}
{% note %}
Note: GPG does not come installed by default on macOS or Windows. To install GPG command line tools, see GnuPG's Download page.
{% endnote %}
{% data reusables.command_line.open_the_multi_os_terminal %} {% data reusables.gpg.list-keys-with-note %} 3. Check the command output to see if you have a GPG key pair. * If there are no GPG key pairs or you don't want to use any that are available for signing commits and tags, then generate a new GPG key. * If there's an existing GPG key pair and you want to use it to sign commits and tags, then add your GPG key to your GitHub account.