Why would enterprise or organization administrators restrict who can create repositories?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Creation policies fight repo sprawl and keep new repos under governance. They don't exile code to personal accounts or kill pull requests site-wide.
Full explanation below image
Full Explanation
Repository creation policies limit which roles may create repositories at organization or enterprise scope. The goal is governance: fewer orphaned projects, clearer ownership, mandatory templates or custom properties, and consistent application of security defaults such as secret scanning or rulesets. Restricting creation does not push code into personal accounts as a requirement, does not alter Git pack negotiation internals, and does not disable pull requests globally. Admins often combine creation limits with template repositories, internal visibility defaults, and automated provisioning through APIs or Terraform so agility remains while uncontrolled sprawl declines.