Skip to content
Discussion options

You must be logged in to vote

The rename → new org → transfer order is what the docs recommend, so you didn't do anything weird. What bit you is namespace retirement: when you rename an account, GitHub permanently retires OLD-OWNER/REPO-NAME for any public repo that had more than 100 clones or more than 100 Actions uses in the week before the rename, or that contains a Marketplace action. Forks and stars don't factor in. I'm not sure whether CI checkouts count as clones, but Insights → Traffic shows the clone numbers if you want to check.

So orgName/repoName is blocked and there's nothing on your side that releases it. Two options:

  • transfer it under a different repo name (rename it in your personal account first, the…

Replies: 4 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by Maker-Lab-Kids
Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug GitHub or a GitHub feature is not working as intended Repositories The core of version-controlled code storage Welcome 🎉 Used to greet and highlight first-time discussion participants. Welcome to the community! source:ui Discussions created via Community GitHub templates
3 participants