Fix article headings before running H3->H2 script (#19663)
* Fix 'How does upgrading or downgrading affect the billing process?' * Fix 'About Git Large File StorageAbout Git Large File Storage' * Fix 'What happens to forks when a repository is deleted or changes visibility?' * Fix 'Audited actions' * Fix 'About managing vulnerable dependencies' * Fix 'GitHub Connect Addendum to the GitHub Enterprise License Agreement' * Fix 'GitHub Government Takedown Policy' * Fix 'GitHub Username Policy' * Fix 'Using the Explorer' * Fix 'Resource limitations'
This commit is contained in:
@@ -13,27 +13,27 @@ versions:
|
||||
topics:
|
||||
- Pull requests
|
||||
---
|
||||
{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
|
||||
{% data reusables.repositories.deleted_forks_from_private_repositories_warning %}
|
||||
|
||||
#### Deleting a private repository
|
||||
### Deleting a private repository
|
||||
|
||||
When you delete a private repository, all of its private forks are also deleted.
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
|
||||
|
||||
#### Deleting a public repository
|
||||
### Deleting a public repository
|
||||
|
||||
When you delete a public repository, one of the existing public forks is chosen to be the new parent repository. All other repositories are forked off of this new parent and subsequent pull requests go to this new parent.
|
||||
|
||||
{% endif %}
|
||||
|
||||
#### Private forks and permissions
|
||||
### Private forks and permissions
|
||||
|
||||
{% data reusables.repositories.private_forks_inherit_permissions %}
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or enterpriseServerVersions contains currentVersion %}
|
||||
|
||||
#### Changing a public repository to a private repository
|
||||
### Changing a public repository to a private repository
|
||||
|
||||
If a public repository is made private, its public forks are split off into a new network. As with deleting a public repository, one of the existing public forks is chosen to be the new parent repository and all other repositories are forked off of this new parent. Subsequent pull requests go to this new parent.
|
||||
|
||||
@@ -43,15 +43,15 @@ In other words, a public repository's forks will remain public in their own sepa
|
||||
If a public repository has anonymous Git read access enabled and the repository is made private, all of the repository's forks will lose anonymous Git read access and return to the default disabled setting. If a forked repository is made public, repository administrators can re-enable anonymous Git read access. For more information, see "[Enabling anonymous Git read access for a repository](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)."
|
||||
{% endif %}
|
||||
|
||||
##### Deleting the private repository
|
||||
#### Deleting the private repository
|
||||
|
||||
If a public repository is made private and then deleted, its public forks will continue to exist in a separate network.
|
||||
|
||||
#### Changing a private repository to a public repository
|
||||
### 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 parent 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.
|
||||
|
||||
##### Deleting the public repository
|
||||
#### Deleting the public repository
|
||||
|
||||
If a private repository is made public and then deleted, its private forks will continue to exist as standalone private repositories in separate networks.
|
||||
|
||||
@@ -59,7 +59,7 @@ If a private repository is made public and then deleted, its private forks will
|
||||
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}
|
||||
|
||||
#### Changing the visibility of an internal repository
|
||||
### Changing the visibility of an internal repository
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -69,7 +69,7 @@ If a private repository is made public and then deleted, its private forks will
|
||||
|
||||
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 user account will remain private.
|
||||
|
||||
##### Deleting the internal repository
|
||||
#### Deleting the internal repository
|
||||
|
||||
If you change the visibility of an internal repository and then delete the repository, the forks will continue to exist in a separate network.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user