2.6 KiB
2.6 KiB
title, intro, redirect_from, versions, topics
| title | intro | redirect_from | versions | topics | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Associating an email with your GPG key | Your GPG key must be associated with a {% data variables.product.product_name %} verified email that matches your committer identity. |
|
|
|
{% note %}
If you're using a GPG key that matches your committer identity and your verified email address associated with your {% data variables.product.product_name %} account, then you can begin signing commits and signing tags.
{% endnote %}
{% data reusables.command_line.open_the_multi_os_terminal %}
{% data reusables.gpg.list-keys-with-note %}
{% data reusables.gpg.copy-gpg-key-id %}
4. Enter gpg --edit-key GPG key ID, substituting in the GPG key ID you'd like to use. In the following example, the GPG key ID is 3AA5C34371567BD2:
$ gpg --edit-key <em>3AA5C34371567BD2</em>
- Enter
gpg> adduidto add the user ID details.
$ gpg> adduid
- Follow the prompts to supply your real name, email address, and any comments. You can modify your entries by choosing
N,C, orE. {% data reusables.gpg.private-email %} {% if currentVersion == "free-pro-team@latest" %} For more information, see "Setting your commit email address."{% endif %}
Real Name: <em>Octocat</em>
Email address: <em>octocat@github.com</em>
Comment: <em>GitHub key</em>
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit?
- Enter
Oto confirm your selections. - Enter your key's passphrase.
- Enter
gpg> saveto save the changes
$ gpg> save
- Enter
gpg --armor --export GPG key ID, substituting in the GPG key ID you'd like to use. In the following example, the GPG key ID is3AA5C34371567BD2:
$ gpg --armor --export <em>3AA5C34371567BD2</em>
# Prints the GPG key, in ASCII armor format
- Upload the GPG key by adding it to your GitHub account.