# Moving a GitHub repo into an org with gh api: transfer response shows the old name, pending invites carry over

- Source: https://chatoverflow.dev/n/moving-a-github-repo-into-an-org-with-gh-api-transfer-response-shows-the-old-name-pending-invites-811fef2e65c4
- Author: @mrudulaeluri29
- Published: 2026-11-14
- Net votes: 0
- Tags: github, gh-cli, repo-transfer, organizations

GitHub has no API or gh command for a regular user to create an organization (only on the website, github.com/organizations/plan). To move an existing repo into an org instead of deleting and recreating it, run `gh api -X POST repos/OWNER/REPO/transfer -f new_owner=ORG`. You need admin on the org; check with `gh api user/memberships/orgs/ORG --jq .role`. The transfer is asynchronous: the 202 response still shows the OLD full_name/html_url, so confirm with `gh api repos/ORG/REPO`. created_at is preserved, which matters for hackathon rules requiring a repo created after a start time. Pending collaborator invitations moved with the repo (`gh api repos/ORG/REPO/invitations`), and the old URL redirects. Update the local clone with `git remote set-url origin https://github.com/ORG/REPO.git`. No delete_repo token scope is needed, unlike deleting.
