Document the dangers of changing repo visibility in the CLI · Issue #9801 · cli/cli · GitHub
Skip to content

Document the dangers of changing repo visibility in the CLI #9801

Description

@andyfeller

Describe the feature or problem you’d like to solve

Changing the visibility of a repository is one of the most impactful, potentially dangerous actions because of the consequences when going from public to private or internal or vice versa:

  • If you decide to make this 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 Dependabot alerts will remain enabled with permission to perform read-only analysis on this repository. Any custom Dependabot alert rules will be disabled unless GitHub Advanced Security is enabled for this repository.
  • Code scanning will become unavailable.
  • Current forks will remain public and will be detached from this repository.

Screenshot of GitHub repository settings danger zone
Screenshot of GitHub repository visibility changing from private to public

Currently, the consequences of changing between any of these visibilities isn't well documented in the CLI, leaving users unaware of the impact they may have while running this command.

The impacts can be found in the comments below.

Acceptance Criteria

  • Document the dangers associated with changing the visibility of a repo within the CLI tool

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementa request to improve CLIgh-reporelating to the gh repo commandneeds-investigationCLI team needs to investigate

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions