From 6bc03239a06382a8ea116cbd112301c8924278c7 Mon Sep 17 00:00:00 2001 From: Ror <47309835+rorcores@users.noreply.github.com> Date: Wed, 15 Sep 2021 13:39:44 -0700 Subject: [PATCH] Update README.md added 'Deploy Key' for more clarity --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a6b64dd..7725d64 100644 --- a/README.md +++ b/README.md @@ -22,7 +22,7 @@ GitHub Actions only have access to the repository they run for. So, in order to 1. Generate a new SSH key with sufficient access privileges. For security reasons, don't use your personal SSH key but set up a dedicated one for use in GitHub Actions. See below for a few hints if you are unsure about this step. 2. Make sure you don't have a passphrase set on the private key. -3. Add the public SSH key to the private repository you are pulling from during the Github Action. +3. Add the public SSH key to the private repository you are pulling from during the Github Action as a 'Deploy Key'. 4. Add the private SSH key to the repository triggering the Github Action: * In your repository, go to the *Settings > Secrets* menu and create a new secret. In this example, we'll call it `SSH_PRIVATE_KEY`. * Put the contents of the *private* SSH key file into the contents field.