{"id":56840,"date":"2023-03-12T13:57:43","date_gmt":"2023-03-12T08:27:43","guid":{"rendered":"https:\/\/2thenew.xyz\/blog\/?p=56840"},"modified":"2023-03-14T14:14:27","modified_gmt":"2023-03-14T08:44:27","slug":"git-add-multiple-repositoriesbitbucket-github-to-the-same-project","status":"publish","type":"post","link":"https:\/\/2thenew.xyz\/blog\/git-add-multiple-repositoriesbitbucket-github-to-the-same-project\/","title":{"rendered":"Git: Add multiple repositories(Bitbucket, Github) to the same project."},"content":{"rendered":"

In this blog, we are going to learn about an important feature (migration across repositories providers) of one of the most common technologies we came across in our day-to-day development, GIT.<\/p>\n

I mainly used to do R&D work on my private repositories, on bitbucket, as it supports unlimited private repositories space. But after some time, when I started contributing to open source, I realized that GitHub is better at it and I want to use some of my already done work. Therefore, I need to migrate some of my repositories to bitbucket.<\/p>\n

Prerequisites: a Bitbucket repository (where original code is present) and a GitHub repository(target repository where the code is to be moved).<\/p>\n

Let’s see how I achieve it:<\/p>\n

Step 1:\u00a0 Clone the code from bitbucket to your local system using the git clone command.<\/p>\n

\"Blog<\/p>\n

\n
git clone https:\/\/dheerajgupta217@bitbucket.org\/dheerajgupta217\/bitbucketrepo.<\/pre>\n
Output<\/span>:<\/p>\n
git
\nCloning into ‘bitbucketrepo’…
\nremote: Enumerating objects: 13, done.
\nremote: Counting objects: 100% (13\/13), done.
\nremote: Compressing objects: 100% (12\/12), done.
\nremote: Total 13 (delta 2), reused 0 (delta 0), pack-reused 0
\nUnpacking objects: 100% (13\/13), 1.96 KiB | 49.00 KiB\/s, done.<\/p><\/blockquote>\n
Step 2:\u00a0 Move to the location where the project is cloned<\/p>\n
\n
 cd bitbucketrepo\/<\/pre>\n<\/blockquote>\n
Step 3:\u00a0 Add the secondary repository origin with a different name (I used github<\/strong> for simplicity reasons)<\/p>\n
\n
git remote add github<\/strong> https:\/\/github.com\/dheerajgupta217\/secondary_repository.<\/pre>\n<\/blockquote>\n
Step 4:\u00a0 Move your master to the new repository<\/p>\n
\n
 git push github master<\/pre>\n
Output:<\/span><\/p>\n
Enumerating objects: 13, done.
\nCounting objects: 100% (13\/13), done.
\nDelta compression using up to 8 threads
\nCompressing objects: 100% (12\/12), done.
\nWriting objects: 100% (13\/13), 1.98 KiB | 1015.00 KiB\/s, done.
\nTotal 13 (delta 2), reused 0 (delta 0), pack-reused 0
\nremote: Resolving deltas: 100% (2\/2), done.
\nTo https:\/\/github.com\/dheerajgupta217\/secondary_repository.git
\n* [new branch] master -> master<\/p><\/blockquote>\n
Step 5:\u00a0 Set the URL of the new repository to the origin added.<\/p>\n
\n
 git remote set-url github https:\/\/github.com\/dheerajgupta217\/secondary_repository<\/pre>\n<\/blockquote>\n
Step 6:\u00a0 Check if both repositories are working.<\/p>\n
\n
git branch -a<\/pre>\n
Output<\/span>:<\/p>\n
* master\r\nremotes\/github\/master\r\nremotes\/origin\/HEAD -> origin\/master\r\nremotes\/origin\/master<\/pre>\n<\/blockquote>\n
\"Github<\/p>\n
Voila, the git migration is done<\/p>\n
Testing the migration activity:<\/p>\n
Step 1: Add a new branch to the bitbucket and push it.<\/p>\n
\"Blog<\/p>\n
\n
git checkout -b test_branch\r\ngit push origin test_branch<\/pre>\n<\/blockquote>\n
\"Blog<\/p>\n
Step 2: Push the same branch to GitHub now.<\/p>\n
\n
git push github test_branch<\/pre>\n<\/blockquote>\n
Output<\/span>:<\/p>\n
\n
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0\r\nremote:\r\nremote: Create a pull request for 'test_branch' on GitHub by visiting:\r\nremote: https:\/\/github.com\/dheerajgupta217\/secondary_repository\/pull\/new\/test_branch\r\nremote:\r\nTo https:\/\/github.com\/dheerajgupta217\/secondary_repository\r\n* [new branch] test_branch -> test_branch<\/pre>\n<\/blockquote>\n
\"Blog<\/p>\n
The branch and the code must be created in GitHub.<\/p>\n
Use Case:<\/strong><\/span><\/p>\n
Recently for one of our clients, this use case is being used where the code is needed to be moved to code-commit form bitbucket and the client requires his old code as well intact. Migration for it was achieved using the below-mentioned steps.<\/p>\n
\"Blog<\/p>\n
<\/div>","protected":false},"excerpt":{"rendered":"
In this blog, we are going to learn about an important feature (migration across repositories providers) of one of the most common technologies we came across in our day-to-day development, GIT. I mainly used to do R&D work on my private repositories, on bitbucket, as it supports unlimited private repositories space. But after some time, […]<\/p>\n","protected":false},"author":1352,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":125,"footnotes":""},"categories":[2348,1],"tags":[4279,375,503,5130],"class_list":["post-56840","post","type-post","status-publish","format-standard","hentry","category-devops-technology","category-technology","tag-bitbucket","tag-git","tag-github","tag-migration-in-repos"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t