From 722fb7b4b4ebe582b9fe3a56232a659ecd90714e Mon Sep 17 00:00:00 2001
From: Heiko Kiesel <heiko.kiesel@iteratec.com>
Date: Tue, 25 Jul 2023 15:50:28 +0200
Subject: [PATCH] Add explanation on how to add signing key and password to
 github actions

Signed-off-by: Heiko Kiesel <heiko.kiesel@iteratec.com>
---
 release.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/release.md b/release.md
index f0f72074..c6eb3cb7 100644
--- a/release.md
+++ b/release.md
@@ -64,6 +64,22 @@ gpg --import private.key
 gpg --armor --export-secret-keys 40AA7D29EB6DE0667D7E723ADE4725604A739BAF
 ```
 
+In the GitHub Secrets [1], add the output of this command to the `SIGNING_KEY` secret.
+Additionally, you must add the corresponding password in as `SIGNING_PASSWORD`.
+Both can be accessed in a yaml file with `${{ secrets.SIGNING_KEY }}` and `${{ secrets.SIGNING_PASSWORD }}`.
+We pass both these secrets in the `env` block-
+
+For example:
+
+```yaml
+- name: Publish to Maven Central
+  run: ./gradlew publish
+  env:
+    SIGNING_KEY: ${{ secrets.SIGNING_KEY }}
+    SIGNING_PASSWORD: ${{ secrets.SIGNING_PASSWORD }}
+    ...
+```
+
 #### For Password Manager
 
 ```shell