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: learn-pr/github/github-introduction-administration/includes/4-how-github-organization-permission-works.md
+35Lines changed: 35 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,41 @@ After you create a repository with the correct permissions, you can make it a te
26
26
27
27
1. Select **Template repository**.
28
28
29
+
### What is repository forking?
30
+
31
+
Forking is a way to create a personal copy of someone else's repository under your own GitHub account. When you fork a repository, you get your own version that you can freely modify without affecting the original project. This is a common workflow for contributing to open source or experimenting with changes safely.
32
+
33
+
You can also keep your fork up to date by pulling in changes from the original repository, often called the “upstream” repo.
34
+
35
+
Here’s how to fork a repository:
36
+
37
+
1. On GitHub.com, navigate to the main page of the repository you want to fork.
38
+
1. In the upper-right corner, select **Fork**.
39
+
1. Choose an owner for the fork (your personal account or an organization).
40
+
1. Optionally, rename the forked repository or include all branches.
41
+
1. Select **Create fork**.
42
+
43
+
:::image type="content" source="../media/fork-repo-option.png" alt-text="Screenshot showing the fork button in the top-right corner of a GitHub repository." border="false":::
44
+
45
+
### Managing fork permissions (for admins)
46
+
47
+
For organization-owned repositories, administrators can control whether repositories can be forked:
48
+
49
+
-**Public repositories**: Forking is always allowed.
50
+
-**Private repositories**: Forking can be disabled or restricted to organization members only.
51
+
-**Internal repositories**: These can only be forked within the same enterprise account.
52
+
53
+
To configure fork settings:
54
+
55
+
1. Go to the repository’s **Settings**.
56
+
1. Scroll to the **Danger Zone**.
57
+
1. Locate the fork control options and update them as needed.
58
+
59
+
**Tip:** If you disable forking for a private repository, no one (including organization members) will be able to fork it.
60
+
61
+
To learn more, see the GitHub Docs article on [Fork a repo](https://docs.github.com/en/get-started/quickstart/fork-a-repo).
62
+
63
+
29
64
## Ways Users Receive Repository Access
30
65
31
66
### Actions of a User Given a List of Their Repository Permissions
0 commit comments