From 32efa559a3b643df117222e998b2d9ab550b0060 Mon Sep 17 00:00:00 2001 From: Sven Dowideit Date: Fri, 20 Mar 2015 14:09:30 +1000 Subject: [PATCH] Small copy edits Signed-off-by: Sven Dowideit --- docs/sources/docker-hub/builds.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/sources/docker-hub/builds.md b/docs/sources/docker-hub/builds.md index ac62e4f984..1613ad1d4b 100644 --- a/docs/sources/docker-hub/builds.md +++ b/docs/sources/docker-hub/builds.md @@ -67,11 +67,11 @@ If your GitHub repository contains links to private submodules, you'll get an error message in your build. Normally, the Docker Hub sets up a deploy key in your GitHub repository. -Unfortunately, GitHub only allows a deploy key to access one single repository. +Unfortunately, GitHub only allows a repository deploy key to access a single repository. -To work around this, we will be creating a dedicated user account in GitHub to -attach this key to. A key on a GitHub user account can be given read-only -access to all your repositories. +To work around this, you need to create a dedicated user account in GitHub and attach +the automated build's deploy key that account. This dedicated build account +can be limited to read-only access to just the repositories required to build. @@ -91,7 +91,7 @@ access to all your repositories. -
2. This can be accomplished by adding the account to a read-only team on + This can be accomplished by adding the account to a read-only team in the organization(s) where the main GitHub repository and all submodule repositories are kept.