Skip to content

Commit

Permalink
Add warning about stars and watches to repo visibility change docs (#…
Browse files Browse the repository at this point in the history
…53875)

Co-authored-by: Kevin Heis <[email protected]>
Co-authored-by: Sophie <[email protected]>
  • Loading branch information
3 people authored Jan 27, 2025
1 parent c774c23 commit b403b3b
Showing 1 changed file with 6 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,12 @@ If a public repository is made private, its public forks are split off into a ne

In other words, a public repository's forks will remain public in their own separate repository network even after the upstream repository is made private. This allows the fork owners to continue to work and collaborate without interruption. If public forks were not moved into a separate network in this way, the owners of those forks would need to get the appropriate [access permissions](/get-started/learning-about-github/access-permissions-on-github) to pull changes from and submit pull requests to the (now private) upstream repository—even though they didn't need those permissions before.

> [!WARNING]
> * Making a public repository private will permanently remove stars and watchers associated to users that will no longer have access to this repository. If you decide to make the repository public in the future, it will not be possible to restore these stars and watchers, and this will affect its repository rankings.
> * Dependency graph and {% data variables.product.prodname_dependabot_alerts %} will remain enabled with permission to perform read-only analysis on this repository. Any custom {% data variables.product.prodname_dependabot %} alert rules will be disabled unless {% data variables.product.prodname_GH_advanced_security %} is enabled for this repository.
> * {% data variables.product.prodname_code_scanning_caps %} will become unavailable.
> * Current forks will remain public and will be detached from this repository.
{% ifversion ghes %}
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 [AUTOTITLE](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository).
{% endif %}
Expand Down

0 comments on commit b403b3b

Please sign in to comment.