From 81290cdb8c027e945e66c40b9efd912511c40859 Mon Sep 17 00:00:00 2001 From: Dmitry Shibanov Date: Tue, 16 Feb 2021 18:12:46 +0300 Subject: [PATCH] change imported to exported --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index db93c23..14e6d77 100644 --- a/README.md +++ b/README.md @@ -187,7 +187,7 @@ The two `settings.xml` files created from the above example look like the follow If `gpg-private-key` input is provided, the private key will be written to a file in the runner's temp directory, the private key file will be imported into the GPG keychain, and then the file will be promptly removed before proceeding with the rest of the setup process. A cleanup step will remove the imported private key from the GPG keychain after the job completes regardless of the job status. This ensures that the private key is no longer accessible on self-hosted runners and cannot "leak" between jobs (hosted runners are always clean instances). -**GPG key should be imported by: `gpg --armor --export-secret-keys YOUR_ID`** +**GPG key should be exported by: `gpg --armor --export-secret-keys YOUR_ID`** See the help docs on [Publishing a Package](https://help.github.com/en/github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages#publishing-a-package) for more information on the `pom.xml` file.