From 719bcb4f945a58c97eeb644698d5ffc55025bac8 Mon Sep 17 00:00:00 2001 From: Dmitry Shibanov Date: Fri, 12 Feb 2021 16:16:23 +0300 Subject: [PATCH] resolve comments --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 1904450..ae33eb2 100644 --- a/README.md +++ b/README.md @@ -88,7 +88,7 @@ jobs: ### Extra setup for pom.xml: -According to possible issues with `Inappropriate ioctl for device` or `gpg: signing failed: No such file or directory`, Maven GPG Plugin configuration in pom.xml should contain the following: +Maven GPG Plugin configuration in pom.xml file should contain the following structure to avoid possible issues like `Inappropriate ioctl for device` or `gpg: signing failed: No such file or directory`: ``` @@ -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 through: `gpg --armor --export-secret-keys YOUR_ID`** +**GPG key should be imported 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.