Skip to main content

Managing the forking policy for your organization

You can allow or prevent the forking of any private and internal repositories owned by your organization.

Who can use this feature

Organization owners can manage the forking policy for an organization.

By default, new organizations are configured to disallow the forking of private and internal repositories.

If you allow forking of private and internal repositories at the organization level, you can also configure the ability to fork a specific private or internal repository. For more information, see "Managing the forking policy for your repository."

If your organization is owned by an enterprise account, you may not be able to configure this setting for your organization, if an enterprise owner has set a policy at the enterprise level. For more information, see "Enforcing repository management policies in your enterprise."

  1. In the top right corner of GitHub.com, click your profile photo, then click Your organizations. Your organizations in the profile menu
  2. Next to the organization, click Settings. The settings button
  3. Under "Access", click Member privileges. Screenshot of the member privileges tab
  4. Under "Repository forking", select Allow forking of private and internal repositories. Checkbox to allow or disallow forking in the organization
  5. Optionally, if forking is enabled, you can specify where users are allowed to fork repositories. If your organization belongs to a GitHub Enterprise account and a more restrictive default has been selected in the enterprise settings, you won't be able to select the more permissive default in your organization settings. Review the information about changing the setting and choose a policy. Screenshot showing the list of repository forking policy options
  6. Click Save.

Further reading