Skip to content

Commit 722fb7b

Browse files
Heiko KieselWeltraumschaf
Heiko Kiesel
authored andcommitted
Add explanation on how to add signing key and password to github actions
Signed-off-by: Heiko Kiesel <heiko.kiesel@iteratec.com>
1 parent eb72b85 commit 722fb7b

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

release.md

+16
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,22 @@ gpg --import private.key
6464
gpg --armor --export-secret-keys 40AA7D29EB6DE0667D7E723ADE4725604A739BAF
6565
```
6666

67+
In the GitHub Secrets [1], add the output of this command to the `SIGNING_KEY` secret.
68+
Additionally, you must add the corresponding password in as `SIGNING_PASSWORD`.
69+
Both can be accessed in a yaml file with `${{ secrets.SIGNING_KEY }}` and `${{ secrets.SIGNING_PASSWORD }}`.
70+
We pass both these secrets in the `env` block-
71+
72+
For example:
73+
74+
```yaml
75+
- name: Publish to Maven Central
76+
run: ./gradlew publish
77+
env:
78+
SIGNING_KEY: ${{ secrets.SIGNING_KEY }}
79+
SIGNING_PASSWORD: ${{ secrets.SIGNING_PASSWORD }}
80+
...
81+
```
82+
6783
#### For Password Manager
6884

6985
```shell

0 commit comments

Comments
 (0)