This version of GitHub Enterprise Server was discontinued on 2024-09-25. 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 repository

You can allow or prevent the forking of a specific private or internal repository owned by an organization.

Who can use this feature?

People with admin permissions for a repository can manage the forking policy for the repository.

An organization owner must allow forks of private and internal repositories on the organization level before you can allow or disallow forks for a specific repository. For more information, see "Managing the forking policy for your organization."

You can help prevent sensitive information from being exposed by disabling the ability to fork repositories in your organization. For more information, see "Best practices for preventing data leaks in your organization."

  1. On GitHub, navigate to the main page of the repository.

  2. Under your repository name, click Settings. If you cannot see the "Settings" tab, select the dropdown menu, then click Settings.

    Screenshot of a repository header showing the tabs. The "Settings" tab is highlighted by a dark orange outline.

  3. Under "Features", select Allow forking. If you do not have this option, you may not have permissions to control this setting. Check with the owner of the organization that administers the repository or with the owner of the repository about your access.

Further reading