-
-
Save mandiwise/5954bbb2e95c011885ff to your computer and use it in GitHub Desktop.
// Reference: http://www.blackdogfoundry.com/blog/moving-repository-from-bitbucket-to-github/ | |
// See also: http://www.paulund.co.uk/change-url-of-git-repository | |
$ cd $HOME/Code/repo-directory | |
$ git remote rename origin bitbucket | |
$ git remote add origin https://github.com/mandiwise/awesome-new-repo.git | |
$ git push origin master | |
$ git remote rm bitbucket |
I'm not tried yet, btw what about history commit on repo after moved? will it recorded also or it will just begin from zero?
already tried & my commit histories followed. Thank you for your snippet commands
This method is only moving the master branch. I would urge you to use the github built in
Import Repository
tool. Add repo menu in top right hand corner of most screensYou can then change your local repo to point at the new origin.
git remote -v
to print the current settingsgit remote set-url origin [email protected]:username/repo-name.git
to change origin to the new url (ssh style url shown here, use the https style like above if that is what you prefer.)then after that you can optionally add the old remote if you have a need.
The problem with doing a
remote rename
is that any local branches tracking origin will then track bitbucket which may or may not be desirable. Then once you doremote rm
the local branches are left with no remote tracking branch, again this may or may not be desirable.For the purpose of switching from bitbucket to github for which you won't be returning or requiring the ongoing hosting on bitbucket it would be desirable to not rename but simple reassign origin's url with the new github URL.
Thank you so much! This worked perfectly.
Thanks, worked fine! s2
Created a small project to do this - https://github.com/searchspring/bb2gh
awesome! Worked perfectly!
If you're using bitbucket make sure the login is whatever it says in your https://bitbucket.org/account (not your email address) and generate an app password, that worked for me.
Thanks @jstxx it worked for me !
Thanks!!
wow, that was easy! thanks for help!
If you're using bitbucket make sure the login is whatever it says in your https://bitbucket.org/account (not your email address) and generate an app password, that worked for me.
Thanks this worked!
If you're using bitbucket make sure the login is whatever it says in your https://bitbucket.org/account (not your email address) and generate an app password, that worked for me.
Thanks for the tip. it worked for me!
It worked for me, thank you @mandiwise :)
If you're using bitbucket make sure the login is whatever it says in your https://bitbucket.org/account (not your email address) and generate an app password, that worked for me.
Promote this man! This was my problem :)
According to github importer documenation, the following is NOT imported:
- Personal repositories owned by users
- Branch permissions
- Commit comments
- Repository settings
- CI pipelines
This makes the import tool a non-starter for me, my bitbucket repos are all private and I very much want the commit comments.
BTW, this thread may see more activity for awhile.. Atlassian in its wisdom has terminated support for Bitbucket Server effective 5-MAR-2024 (2 weeks from now).
+1 for GitHub import tool. It's easier.
Also, in my case, I needed to create an App password
in my Bitbucket account settings, and use my Bitbucket username and the created token as credentials when importing. (Read & Write)
Finally, just reset the remote url locally git remote set-url origin [email protected]:username/repo-name.git
.
FWIW, Atlassian now tells me that this was a false alarm. Once they figured out how to let me update the expiration date of my credit card, all was fine with my current Bitbucket product. I'm not going to even try to hazard a guess as to its name. The Atlassian site is among the worst I've ever tried to navigate.
If you're using bitbucket make sure the login is whatever it says in your https://bitbucket.org/account (not your email address) and generate an app password, that worked for me.
Give this guy a nobel prize 🙌
I'm not tried yet, btw what about history commit on repo after moved? will it recorded also or it will just begin from zero?