gitee-to-github-migration

Verify gh CLI login with gh auth status, remove existing remotes with git remote remove, then run gh repo create <name> --public --source=. --push to create the GitHub repository and push your code in one step.

Remove the old remotes with git remote remove origin and git remote remove orgin, then add the GitHub URL with git remote add origin and pull with git pull origin main --rebase. Verify with git remote -v.

This error means the GitHub repository already exists with initial commits that conflict with your local history. The documented fix is git push -u origin main --force, but only after confirming the remote content can be overwritten.

The Gitee remote may be misspelled as orgin (missing the letter i), which is a common typo. Run git remote -v to list all remotes, then remove the misspelled one with git remote remove orgin.

Yes, instead of removing the Gitee remote, add GitHub as an additional remote with git remote add github <url>. You can then push to both remotes separately to keep Gitee as a backup copy.