Как изменить тип репозитория github

About repository visibility changes

Organization owners can restrict the ability to change repository visibility to organization owners only. For more information, see «Restricting repository visibility changes in your organization.»

We recommend reviewing the following caveats before you change the visibility of a repository.

Making a repository private

• GitHub will detach public forks of the public repository and put them into a new network. Public forks are not made private.
• If you’re using GitHub Free for personal accounts or organizations, some features won’t be available in the repository after you change the visibility to private. Any published GitHub Pages site will be automatically unpublished. If you added a custom domain to the GitHub Pages site, you should remove or update your DNS records before making the repository private, to avoid the risk of a domain takeover. For more information, see «GitHub’s products and «Managing a custom domain for your GitHub Pages site.»
• GitHub will no longer include the repository in the GitHub Archive Program. For more information, see «About archiving content and data on GitHub.»
• GitHub Advanced Security features, such as code scanning, will stop working. For more information, see «About GitHub Advanced Security.»

Making a repository public

• GitHub will detach private forks and turn them into a standalone private repository. For more information, see «What happens to forks when a repository is deleted or changes visibility?»
• If you’re converting your private repository to a public repository as part of a move toward creating an open source project, see the Open Source Guides for helpful tips and guidelines. You can also take a free course on managing an open source project with GitHub Skills. Once your repository is public, you can also view your repository’s community profile to see whether your project meets best practices for supporting contributors. For more information, see «Viewing your community profile.»
• The repository will automatically gain access to GitHub Advanced Security features.

For information about improving repository security, see «Securing your repository.»

Changing a repository’s visibility

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

2. Under your repository name, click
   Settings.
   

3. Under «Danger Zone», to the right of to «Change repository visibility», click Change visibility.
   

4. Select a visibility.

   

5. To verify that you’re changing the correct repository’s visibility, type the name of the repository you want to change the visibility of.

6. Click I understand, change repository visibility.

   

Further reading

• «About repositories»

Instead of switching back and forth between GitHub repository visibility status (which is possible through the repository settings, section «danger zone»), I would rather establish 2 repositories:

• one public, with only public content
• one private, with a mix of public and private content

That way, you don’t have to wonder, when pushing to a repository, if it is today public or private: you would push to one specific repository (of the two), knowing full well its visibility status.
And you would never expose private content, which, is set to public even a few minutes, … is no longer ever truly private (because it can be cloned, replicated and pushed elsewhere)

That being said, since June 2020, you have an «Updated UI for Changing Repository Visibility «:

You can now set your repository to any available visibility option – public, private, or internal – from a single dialog in the repository’s settings.

Previously, you had to navigate separate sections, buttons, and dialog boxes for changing between public and private, and between private and internal.

See «Setting repository visibility»

(*) «destructuve action» because of the consequences of the visibility change:

• public to private: some features won’t be available in the repository after you change the visibility to private. Any published GitHub Pages site will be automatically unpublished.
  GitHub Advanced Security features, such as code scanning, will stop working

• private to public: GitHub will detach private forks and turn them into a standalone private repository

Note that, since July 10th 2020, the default visibility is private:

Default visibility for new repositories

When you create a repository, you can choose whether it should be private or public.

Now, when you’re signed into GitHub through an organization’s single sign on service and create a new repository through the website navigation, the default selection is Private.

This helps prevent sensitive company data from unintentionally being pushed to public repositories. See the about repository visibility article for more information about this choice.