Tip: Only organization owners can rename an organization. For more information, see "Roles in an organization."
After changing your organization's name, your old organization name becomes available for someone else to claim. When you change your organization's name, most references to your repositories under the old organization name automatically change to the new name. However, some links to your profile won't automatically redirect.
- GitHub automatically redirects references to your repositories. Web links to your organization's existing repositories will continue to work. This can take a few minutes to complete after you initiate the change.
- You can continue pushing your local repositories to the old remote tracking URL without updating it. However, we recommend you update all existing remote repository URLs after changing your organization name. Because your old organization name is available for use by anyone else after you change it, the new organization owner can create repositories that override the redirect entries to your repository. For more information, see "Managing remote repositories."
- Previous Git commits will also be correctly attributed to users within your organization.
- If the account namespace includes any public repositories that contain an action listed on GitHub Marketplace, or that had more than 100 clones or more than 100 uses of GitHub Actions in the week prior to you renaming your account, GitHub permanently retires the old owner name and repository name combination (
OLD-OWNER/REPOSITORY-NAME) when you rename your account.
- If the account namespace includes any packages or container images stored in a GitHub Packages registry, GitHub transfers the packages and container images to the new namespace. By renaming your account, you may break projects that depend on these packages. If the namespace includes any container images that are public and have more than 5,000 downloads, the full former name of these container images (
OLD-NAMESPACE/IMAGE-NAME) is permanently retired when you rename the account to ensure the container image name cannot be reused in the future.
After changing your organization's name:
- Links to your previous organization profile page, such as
https://github.com/previousorgname, will return a 404 error. We recommend you update links to your organization from other sites, such as your LinkedIn or Twitter profiles.
- API requests that use the old organization's name will return a 404 error. We recommend you update the old organization name in your API requests.
- There are no automatic @mention redirects for teams that use the old organization's name.
- If SAML single sign-on (SSO) and/or is enabled for the organization, you must update the organization name in the application for GitHub Enterprise Cloud on your identity provider (IdP). If you don't update the organization name on your IdP, members of the organization will no longer be able to authenticate with your IdP to access the organization's resources. For more information, see "Connecting your identity provider to your organization."
- If SCIM is enabled for the organization, you must update the organization name in the application for GitHub Enterprise Cloud on your identity provider (IdP). If you don't update the organization name within the SCIM settings on your IdP, you will not be able to provision or deprovision users.
In the top right corner of GitHub.com, click your profile photo, then click Your organizations.
Next to the organization, click Settings.
Near the bottom of the settings page, under "Danger zone", click Rename organization.
Read the warning messages, then, if you want to go ahead, click I understand, let's rename my organization.
Type a new name for your organization, then click Change organization's name.