From fd4b6f40b1f9c76f4b8ff24c826ab32ed4d62249 Mon Sep 17 00:00:00 2001 From: RoughB Tier0 Date: Thu, 11 Feb 2021 12:45:09 +0000 Subject: Clarify SSH key setup documentation for private repo setups. Follow-up on https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3C1205952567.133309.1601845746778%40office.mailbox.org%3E --- builds.sr.ht/private-repos.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'builds.sr.ht/private-repos.md') diff --git a/builds.sr.ht/private-repos.md b/builds.sr.ht/private-repos.md index 4f0be0d..403e9ed 100644 --- a/builds.sr.ht/private-repos.md +++ b/builds.sr.ht/private-repos.md @@ -11,8 +11,9 @@ title: Private repos on builds.sr.ht builds.sr.ht can use private repos on git.sr.ht and elsewhere, but you have to configure each job with an SSH key that has access to your account. -1. Generate an SSH key (without a passphrase) and [add it to your account](https://meta.sr.ht/keys) -1. Add a secret using the [secrets management page](https://builds.sr.ht/secrets) +1. Generate an SSH key (without a passphrase) +1. Add the public key [to your account](https://meta.sr.ht/keys) +1. Add the private key as a secret using the [secrets management page](https://builds.sr.ht/secrets) 1. Copy the secret's UUID into your build manifest's secrets list. 1. Update your sources list to use the SSH clone URL - not the https clone URL. -- cgit