Эта версия GitHub Enterprise Server была прекращена 2024-03-26. Исправления выпускаться не будут даже при критических проблемах безопасности. Для повышения производительности, повышения безопасности и новых функций выполните обновление до последней версии GitHub Enterprise Server. Чтобы получить справку по обновлению, обратитесь в службу поддержки GitHub Enterprise.

Управление политикой ветвления для вашей организации

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

Кто эту функцию можно использовать?

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 Enterprise Server, select your profile photo, then click Your organizations.

    Screenshot of the dropdown menu under @octocat's profile picture. "Your organizations" is outlined in dark orange.

  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