Skip to content

Commit

Permalink
Small copy edits
Browse files Browse the repository at this point in the history
Signed-off-by: Sven Dowideit <[email protected]>
  • Loading branch information
SvenDowideit committed Mar 20, 2015
1 parent cf0634b commit 32efa55
Showing 1 changed file with 5 additions and 5 deletions.
10 changes: 5 additions & 5 deletions docs/sources/docker-hub/builds.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<table class="table table-bordered">
<thead>
Expand All @@ -91,7 +91,7 @@ access to all your repositories.
<tr>
<td>2.</td>
<td><img src="/docker-hub/hub-images/gh_team_members.png"></td>
<td>This can be accomplished by adding the account to a read-only team on
<td>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.</td>
</tr>
Expand Down

0 comments on commit 32efa55

Please sign in to comment.