From b75d5cee7487837a9a4e4ea5bca54d29b2d1ab33 Mon Sep 17 00:00:00 2001 From: Snir Sheriber Date: Tue, 31 May 2022 15:46:17 +0300 Subject: [PATCH] docs: update release process github token instructions and fix the gpg generating key url Signed-off-by: Snir Sheriber --- docs/Release-Process.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/Release-Process.md b/docs/Release-Process.md index 7e8dfe3290..7dcfb84a30 100644 --- a/docs/Release-Process.md +++ b/docs/Release-Process.md @@ -4,11 +4,11 @@ ## Requirements - [hub](https://github.com/github/hub) - * Using an [application token](https://github.com/settings/tokens) is required for hub. + * Using an [application token](https://github.com/settings/tokens) is required for hub (set to a GITHUB_TOKEN environment variable). - GitHub permissions to push tags and create releases in Kata repositories. -- GPG configured to sign git tags. https://help.github.com/articles/generating-a-new-gpg-key/ +- GPG configured to sign git tags. https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key - You should configure your GitHub to use your ssh keys (to push to branches). See https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/. * As an alternative, configure hub to push and fork with HTTPS, `git config --global hub.protocol https` (Not tested yet) *