Skip to content

Commit

Permalink
Add list of consequences for changing repo visibility (#52883)
Browse files Browse the repository at this point in the history
Co-authored-by: Siara <108543037+SiaraMist@users.noreply.github.com>
  • Loading branch information
jc-clark and SiaraMist authored Oct 25, 2024
1 parent b49665b commit 69005e9
Showing 1 changed file with 52 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -81,6 +81,58 @@ We recommend reviewing the following caveats before you change the visibility of

For information about improving repository security, see "[AUTOTITLE](/code-security/getting-started/securing-your-repository)."{% endif %}

## Consequences of changing a repository's visibility

>[!CAUTION]Before you change your repository's visibility, understand the consequences of this change.
### Changing from public to private

Stars and watchers for this repository will be permanently erased, which will affect repository rankings.
* Custom {% data variables.product.prodname_dependabot %} alert rules will be disabled unless {% data variables.product.prodname_GH_advanced_security %} is enabled for this repository. Dependency graph and {% data variables.product.prodname_dependabot_alerts %} will remain enabled with permission to perform read-only analysis on this repository.
* Code scanning will become unavailable.
* Current forks will remain public and will be detached from this repository.

### Changing from private to public

* The code will be visible to everyone who can visit {% data variables.product.prodname_dotcom_the_website %}.
* Anyone can fork your repository.
* All push rulesets will be disabled.
* Your changes will be published as activity.
* Actions history and logs will be visible to everyone.
* Stars and watchers for this repository will be permanently erased.

{% ifversion ghes or ghec %}

### Changing from private to internal

* All members of the enterprise will be given read access.
* Outside collaborators can no longer be added to forks unless they're added to the root.
* Stars and watchers for this repository will be permanently erased.

### Changing from internal to private

* Stars and watchers for this repository will be permanently erased, which will affect repository rankings.
* Custom {% data variables.product.prodname_dependabot %} alert rules will be disabled unless GitHub Advanced Security is enabled for this repository. Dependency graph and {% data variables.product.prodname_dependabot_alerts %} will remain enabled with permission to perform read-only analysis on this repository.
* Code scanning will become unavailable.
* Current forks will remain public and will be detached from this repository.

### Changing from internal to public

* The code will be visible to everyone who can visit {% data variables.product.prodname_dotcom_the_website %}.
* Anyone can fork your repository.
* All push rulesets will be disabled.
* Your changes will be published as activity.
* Actions history and logs will be visible to everyone.
* Stars and watchers for this repository will be permanently erased.

### Changing from public to internal

* All members of the enterprise will be given read access.
* Outside collaborators can no longer be added to forks unless they're added to the root.
* Stars and watchers for this repository will be permanently erased.

{% endif %}

## Changing a repository's visibility

{% data reusables.repositories.navigate-to-repo %}
Expand Down

0 comments on commit 69005e9

Please sign in to comment.