885da5b3d3
* New Crowdin translations by Github Action * Reset broken translated files to English * Ran script/i18n/homogenize-frontmatter.js * Ran script/fix-translation-errors.js * Reverted translated files with parsing and rendering errors * fix malformed liquid * add next directory to exclude list * currentversion -> currentVersion * fix liquid errors * fix liquid errors * Reset broken translated files to English * Ran script/i18n/homogenize-frontmatter.js * Revert /ja/github/authenticating-to-github/about-authentication-with-saml-single-sign-on * Reset known broken translation files LAST * Run script/i18n/homogenize-frontmatter.js Co-authored-by: Crowdin Bot <support+bot@crowdin.com> Co-authored-by: Rachael Sewell <rachmari@github.com> Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com>
1.6 KiB
1.6 KiB
title, intro, redirect_from, versions, topics
| title | intro | redirect_from | versions | topics | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Checking for existing GPG keys | Before you generate a GPG key, you can check to see if you have any 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.