About migrations for legacy admin teams
By default, all organization members can create repositories. If you restrict repository creation permissions to organization owners, and your organization was created under the legacy organization permissions structure, members of legacy admin teams will still be able to create repositories.
Legacy admin teams are teams that were created with the admin permission level under the legacy organization permissions structure. Members of these teams were able to create repositories for the organization, and we've preserved this ability in the improved organization permissions structure.
You can remove this ability by migrating your legacy admin teams to the improved organization permissions.
For more information, see Repository roles for an organization.
경고
If your organization has disabled repository creation permissions for all members, some members of legacy admin teams may lose repository creation permissions. If your organization has enabled member repository creation, migrating legacy admin teams to improved organization permissions will not affect team members' ability to create repositories.
Migrating all of your organization's legacy admin teams
- In the upper-right corner of GitHub, click your profile picture, then click Organizations.
- Next to the organization, click Settings.
- In the "Access" section of the sidebar, click Team discussions.
- Review your organization's legacy admin teams, then click Migrate all teams.
- Read the information about possible permissions changes for members of these teams, then click Migrate all teams.
Migrating a single admin team
-
In the upper-right corner of GitHub, click your profile picture, then click Organizations.
-
Click the name of your organization.
-
Under your organization name, click Teams.
-
Click the name of the team.
-
In the team description box, click Migrate team.
