8000 style and naming corrections · MACNAYA/developer.github.com@b84cec9 · GitHub
[go: up one dir, main page]

Skip to content

Commit b84cec9

Browse files
committed
style and naming corrections
1 parent c237c01 commit b84cec9

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/guides/managing-deploy-keys.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ A deploy key is an SSH key that is stored on your server and grants access to a
8888

8989
## Machine users
9090

91-
If your server needs to access multiple repositories, you can choose to create a new github account and attach an SSH key that will be used exclusively for automation. Since this github account won't be used by a human, it's called a machine user. You can then [add the machine user as collaborator][collaborator] or [add the machine user to a team][team] with access to the repositories it needs to manipulate. **NOTE**: Adding a machine user as a collaborator always grants read/write access. Adding a machine user to a team grants the permissions of the team.
91+
If your server needs to access multiple repositories, you can choose to create a new GitHub account and attach an SSH key that will be used exclusively for automation. Since this GitHub account won't be used by a human, it's called a machine user. You can then [add the machine user as collaborator][collaborator] or [add the machine user to a team][team] with access to the repositories it needs to manipulate. **NOTE**: Adding a machine user as a collaborator always grants read/write access. Adding a machine user to a team grants the permissions of the team.
9292

9393
<div class="alert">
9494
<p>
@@ -104,7 +104,7 @@ If your server needs to access multiple repositories, you can choose to create a
104104

105105
#### Cons
106106

107-
* Only organizations have access to create teams; therefore only organizations can use them to restrict machine users to read-only access. Individual user-owned repositories always grant read/write to collaborators.
107+
* Only organizations have access to create teams; therefore only organizations can use them to restrict machine users to read-only access. Personal repositories always grant collaborators read/write access.
108108
* Machine user keys, like deploy keys, are usually not protected by a passphrase.
109109

110110
#### Setup

0 commit comments

Comments
 (0)
0