Skip to main content

This version of GitHub Enterprise Server will be discontinued on 2024-06-29. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise Server. For help with the upgrade, contact GitHub Enterprise support.

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."

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 upper-right corner of GitHub, select your profile photo, then click Your organizations.

  2. Next to the organization, click Settings.

  3. In the "Access" section of the sidebar, click Member privileges.

  4. Under "Repository forking", select Allow forking of private and internal repositories.

  5. Optionally, if your organization is owned by an enterprise account, select a policy for where users are allowed to fork repositories.

    If repository forking policy is configured at the enterprise level, you won't be able to select a more permissive policy in your organization settings.

  6. Click Save.

Further reading