This repository was archived by the owner on Nov 1, 2017. It is now read-only.
- Notifications
You must be signed in to change notification settings - Fork1.1k
Clarify access granted by deploy keys vs teams vs collaborators.#704
Merged
gjtorikian merged 2 commits intogithub:masterfromtamsky:clarify-machine-users-vs-deploy-keysJan 28, 2015
Merged
Clarify access granted by deploy keys vs teams vs collaborators.#704
gjtorikian merged 2 commits intogithub:masterfromtamsky:clarify-machine-users-vs-deploy-keysJan 28, 2015
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
…ccess.Clarify difference between machines users on a team vs machines users as collaborator.Clarify machine accounts are 'github user accounts'.Clarify user-owned repos are unable to grant read-only access.
| @@ -88,11 +88,11 @@ A deploy key is an SSH key that is stored on your server and grants access to a | |||
| ## Machine users | |||
| If your server needs to access multiple repositories, you can choose to attach an SSH keyto an automated user account.Since this account won't be used by a human, it's called a machine user. You can then [add the machineaccount as collaborator][collaborator] or [add the machine user to a team][team] with access to the repositories it needs to manipulate. | |||
| If your server needs to access multiple repositories, you can choose tocreate a new github account andattach an SSH keythat will be used exclusively for automation.Since thisgithubaccount won't be used by a human, it's called a machine user.You can then [add the machineuser 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. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Can you capitalizegithub here (and in other instances): GitHub.
Great suggestions. I made a few comments; once those are in, we can merge this up. Thank you! ❇️ |
Updated per suggestions. Thanks! |
gjtorikian added a commit that referenced this pull requestJan 28, 2015
Clarify access granted by deploy keys vs teams vs collaborators.
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Labels
None yet
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'll be the first to admit my changes here are a bit of a guess, but I believe I'm correctly clarifying a concept that wasn't previously clear (at least in this document):
Only through the use of teams can one grant read-only access to a repository.
Teams are only available to organizations.