Skip to content

Commit 9778bc6

Browse files
authored
Merge pull request github#39548 from github/repo-sync
Repo sync
2 parents 80559c7 + 5640679 commit 9778bc6

File tree

4 files changed

+330
-326
lines changed

4 files changed

+330
-326
lines changed

content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-permissions-and-visibility-of-forks.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,10 @@ topics:
1414

1515
{% data reusables.repositories.you-can-fork %}
1616

17-
If you fork a private repository that belongs to a personal account, external collaborators also get access to the fork. If you fork a private {% ifversion ghec or ghes %}or internal {% endif %}repository that belongs to an organization, teams within the organization get access to the fork, but external collaborators do not. You can add an external collaborator to a fork of a private repository that belongs to an organization if you are an owner of that organization or if your organization allows repository administrators to invite external collaborators.{% ifversion ghec or ghes %} You can add an external collaborator to a fork of an internal repository that belongs to an organization if the external collaborator also has access to the upstream repository.{% endif %}
17+
* If you fork a private repository that belongs to a personal account, external collaborators also get access to the fork.
18+
* If you fork a private {% ifversion ghec or ghes %}or internal {% endif %}repository that belongs to an organization, teams within the organization get access to the fork, but external collaborators do not.
19+
* {% ifversion ghes %} You can add an external collaborator to a fork of a private repository that belongs to an organization if you are an owner of that organization or if your organization allows repository administrators to invite external collaborators.{% endif %}{% ifversion fpt or ghec %} You can add an external collaborator to a fork of a private repository owned by an organization if you are an organization owner, or if your organization allows repository administrators to invite external collaborators, and the external collaborator also has access to the upstream repository.{% endif %}
20+
{% ifversion ghec or ghes %} * You can add an external collaborator to a fork of an internal repository that belongs to an organization if the external collaborator also has access to the upstream repository.{% endif %}
1821

1922
{% ifversion fpt or ghec %}
2023

@@ -64,6 +67,7 @@ If you work with forks, or if you're the owner of a repository or organization t
6467
### About forks within an organization
6568

6669
Forks within the same organization copy the collaborators and team settings of their upstream repositories. If a repository is owned by an organization:
70+
6771
* That organization controls the permissions of its forks.
6872
* Any teams from the upstream permission structure that exist and are visible in the target organization or user namespace will have their permissions copied.
6973
* Admin permissions remain with the upstream owner, except when a user forks into a different organization.

0 commit comments

Comments
 (0)