Register
Login
Resources
Docs Blog Datasets Glossary Case Studies Tutorials & Webinars
Product
Data Engine LLMs Platform Enterprise
Pricing Explore
Connect to our Discord channel

managing-the-forking-policy-for-your-repository.md 1.7 KB

You have to be logged in to leave a comment. Sign In
title intro redirect_from permissions versions
Managing the forking policy for your repository You can allow or prevent the forking of a specific private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} or internal{% endif %} repository owned by an organization. [/articles/allowing-people-to-fork-a-private-repository-owned-by-your-organization /github/administering-a-repository/allowing-people-to-fork-a-private-repository-owned-by-your-organization] People with admin permissions for a repository can manage the forking policy for the repository. [{free-pro-team *} {enterprise-server *} {github-ae *}]

An organization owner must allow forks of private{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %} and internal{% endif %} 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."

{% data reusables.organizations.internal-repos-enterprise %}

{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} 3. Under "Features", select Allow forking. Checkbox to allow or disallow forking of a private repository

Further reading

Tip!

Press p or to see the previous file or, n or to see the next file

Comments

Loading...