You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/pull-requests/collaborating-with-pull-requests/working-with-forks/about-permissions-and-visibility-of-forks.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,3 +68,11 @@ Forks within the same organization copy the collaborators and team settings of t
68
68
* Any teams from the upstream permission structure that exist and are visible in the target organization or user namespace will have their permissions copied.
69
69
* Admin permissions remain with the upstream owner, except when a user forks into a different organization.
70
70
* If that repository is forked to a user namespace, the organization maintains admin permissions and any teams with access maintain access.
71
+
72
+
{% ifversion ghec or ghes %}
73
+
74
+
### About forks within an enterprise
75
+
76
+
Internal repositories only support a single level of forking, it is not possible to fork a private fork of an internal repository. This is intentional to simplify access and management for internal repositories which have enterprise-wide access. This differs from the behavior of public and private repositories, that allow nested forking.
0 commit comments