1
0
mirror of synced 2026-02-03 00:02:00 -05:00

Merge pull request #28945 from github/repo-sync

Repo sync
This commit is contained in:
docs-bot
2023-10-06 01:33:41 -07:00
committed by GitHub

View File

@@ -52,7 +52,7 @@ If a public repository is made private and then deleted, its public forks will c
## Changing a private repository to a public repository
If a private repository is made public, each of its private forks is turned into a standalone private repository and becomes the upstream of its own new repository network. Private forks are never automatically made public because they could contain sensitive commits that shouldn't be exposed publicly.
When you change a private repository to public, all the commits in that repository, including any commits made in the repositories it was forked into, will be visible to everyone. However, the private forks will not automatically become public. Instead, each private fork will become a separate private repository and create its own independent network of repositories. Any new changes made to these networks will not be accessible from the original repository.
### Deleting the public repository
@@ -64,7 +64,7 @@ If a private repository is made public and then deleted, its private forks will
## Changing the visibility of an internal repository
When you change a private repository to public, all the commits in that repository, including any commits made in the repositories it was forked into, will be visible to everyone. However, the private forks will not automatically become public. Instead, each private fork will become a separate private repository and create its own independent network of repositories. Any new changes made to these networks will not be accessible from the original repository.
If the policy for your enterprise permits forking, any fork of an internal repository will be private. If you change the visibility of an internal repository, any fork owned by an organization or personal account will remain private.
### Deleting the internal repository