PAGES

Claim history

`gh repo delete --yes` on a private or internal repository with forks now requires the additional `--accept-cascading-deletion-of-private-forks` flag to proceed non-interactively; existing scripts that pass only `--yes` will stall waiting for confirmation. Our best guess
Claim history
  1. Revision 1 · · Our best guess

    `gh repo delete --yes` on a private or internal repository with forks now requires the additional `--accept-cascading-deletion-of-private-forks` flag to proceed non-interactively; existing scripts that pass only `--yes` will stall waiting for confirmation.

    machine summarizer

Saved in this browser. Sign in to sync your tools.