From d5c26c68cb518c83d84a97f707243437fe1dd81c Mon Sep 17 00:00:00 2001 From: Hector Alfaro Date: Mon, 20 May 2019 23:45:34 +0200 Subject: [PATCH 1/4] add info about internal visibility --- responses/02_repo-owner-answer.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/responses/02_repo-owner-answer.md b/responses/02_repo-owner-answer.md index 2abc358..b229f0a 100644 --- a/responses/02_repo-owner-answer.md +++ b/responses/02_repo-owner-answer.md @@ -7,11 +7,11 @@ A repository _does_ exist at githubtraining/training-manual, but it is private.
Why can't you see it then? Review the Files Changed tab and see if you can figure it out. Collapse this text if you'd like an explanation. -The repository `training-manual` in the @githubtraining organization is private. It's only visible to members of that organization. If you're not a member of the organization, it'll appear like the repository doesn't exist to you. This is an example of why having the right ownership structure is important. Having too many organizations with restrictive permissions silos and isolates each organization's work. +The repository `training-manual` in the @githubtraining organization is private. There are three types of repository visiility: public, internal, and private. Our repository, `githubtraining/training-manual`, isn't public. It could be internal, which means only members of the organizations that an account owns will see it, or it could be private, which means only teams and individuals that have been granted access to it can see it. Otherwise, it'll appear like the repository doesn't exist to you. This is an example of why having the right ownership structure is important. Having too many organizations with restrictive permissions silos and isolates each organization's work. Here are some recommendations based on some :sparkles: use of GitHub that we've seen: -- Aim for as few organizations as possible. Remember, each organization is a black box to those outside of that organization. +- Use the internal visibility (currently in beta) if you're working on behalf of an account with multiple organizations - Name your repositories in a meaningful manner. Usually a simple project or application name will suffice.
From b9ed6d74f93c9fd7d9770464204dcd31ae88bdc2 Mon Sep 17 00:00:00 2001 From: Cynthia Rich Date: Tue, 21 May 2019 20:43:16 -0400 Subject: [PATCH 2/4] fix formatting of detail block --- responses/02_repo-owner-answer.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/responses/02_repo-owner-answer.md b/responses/02_repo-owner-answer.md index b229f0a..d2dabd9 100644 --- a/responses/02_repo-owner-answer.md +++ b/responses/02_repo-owner-answer.md @@ -5,15 +5,16 @@ A repository _does_ exist at githubtraining/training-manual, but it is private. ![gif of repository, pointing to ownership by githubtraining organization, and to a private visibility](https://user-images.githubusercontent.com/6351798/56159957-32413700-5f83-11e9-90f6-c1b64ade39c4.gif)
-Why can't you see it then? Review the Files Changed tab and see if you can figure it out. Collapse this text if you'd like an explanation. +Why can't you see it then? Review the Files Changed tab and see if you can figure it out. Expand this text if you'd like an explanation. + +## Understanding repository visibility The repository `training-manual` in the @githubtraining organization is private. There are three types of repository visiility: public, internal, and private. Our repository, `githubtraining/training-manual`, isn't public. It could be internal, which means only members of the organizations that an account owns will see it, or it could be private, which means only teams and individuals that have been granted access to it can see it. Otherwise, it'll appear like the repository doesn't exist to you. This is an example of why having the right ownership structure is important. Having too many organizations with restrictive permissions silos and isolates each organization's work. - Here are some recommendations based on some :sparkles: use of GitHub that we've seen: - Use the internal visibility (currently in beta) if you're working on behalf of an account with multiple organizations - Name your repositories in a meaningful manner. Usually a simple project or application name will suffice. - +
Please merge this pull request. From 250c55a880281031343601b1f6b00443de1b501f Mon Sep 17 00:00:00 2001 From: Cynthia Rich Date: Tue, 21 May 2019 20:50:05 -0400 Subject: [PATCH 3/4] tweaks to visibility text --- responses/02_repo-owner-answer.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/responses/02_repo-owner-answer.md b/responses/02_repo-owner-answer.md index d2dabd9..c3a0bd8 100644 --- a/responses/02_repo-owner-answer.md +++ b/responses/02_repo-owner-answer.md @@ -9,7 +9,11 @@ A repository _does_ exist at githubtraining/training-manual, but it is private. ## Understanding repository visibility -The repository `training-manual` in the @githubtraining organization is private. There are three types of repository visiility: public, internal, and private. Our repository, `githubtraining/training-manual`, isn't public. It could be internal, which means only members of the organizations that an account owns will see it, or it could be private, which means only teams and individuals that have been granted access to it can see it. Otherwise, it'll appear like the repository doesn't exist to you. This is an example of why having the right ownership structure is important. Having too many organizations with restrictive permissions silos and isolates each organization's work. +There are three types of repository visiility: **public, internal, and private**. + +Our repository, `githubtraining/training-manual`, isn't public. It could be internal, which means only members of the organizations that an account owns will see it, or it could be private, which means only teams and individuals that have been granted access to it can see it. + +This is an example of why having the right ownership structure is important. Otherwise, it can be difficult for members of your team to find and contribute to projects. Having too many disconnected organizations with restrictive permissions silos and isolates each organization's work. Here are some recommendations based on some :sparkles: use of GitHub that we've seen: - Use the internal visibility (currently in beta) if you're working on behalf of an account with multiple organizations From bbd11a28cd363523daa98bb8f8347c49b62ef5a4 Mon Sep 17 00:00:00 2001 From: Hector Alfaro Date: Thu, 23 May 2019 11:03:01 +0200 Subject: [PATCH 4/4] add link to enterprise accounts --- responses/02_repo-owner-answer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/responses/02_repo-owner-answer.md b/responses/02_repo-owner-answer.md index c3a0bd8..00b0f78 100644 --- a/responses/02_repo-owner-answer.md +++ b/responses/02_repo-owner-answer.md @@ -16,7 +16,7 @@ Our repository, `githubtraining/training-manual`, isn't public. It could be inte This is an example of why having the right ownership structure is important. Otherwise, it can be difficult for members of your team to find and contribute to projects. Having too many disconnected organizations with restrictive permissions silos and isolates each organization's work. Here are some recommendations based on some :sparkles: use of GitHub that we've seen: -- Use the internal visibility (currently in beta) if you're working on behalf of an account with multiple organizations +- Use the internal visibility (currently in beta) if you're working on behalf of an [enterprise account](https://help.github.com/en/articles/about-enterprise-accounts). - Name your repositories in a meaningful manner. Usually a simple project or application name will suffice.