4.1 KiB
| title | date | lastmod | draft | keywords | description | tags | categories | author | comment | toc | autoCollapseToc | postMetaInFooter | hiddenFromHomePage | contentCopyright | reward | mathjax | mathjaxEnableSingleDollar | mathjaxEnableAutoNumber | hideHeaderAndFooter | flowchartDiagrams | sequenceDiagrams | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Push Git Repo to Two Remotes | 2023-06-24T18:15:43+05:30 | 2023-06-24T18:15:43+05:30 | false |
|
|
|
false | true | false | true | false | false | false | false | false | false | false |
|
|
Sometimes you may want to push your code to two different remote repositories, for example, if you want to use one service for hosting your code and another for deploying it. In this post, I will show you how to do that using git.
Adding Multiple Push URLs
The easiest way to push your code to two remotes is to add multiple push URLs for a given remote. For example, if you have a remote called origin that points to your main repository, you can add another push URL for a different repository using this command:
git remote set-url --add --push origin git://existing/repo.git
git remote set-url --add --push origin git://another/repo.git
This will add a second push URL to your origin remote, so when you run git push origin, it will push your code to both repositories. You can verify the current push URLs for a remote by running git remote -v.
You can add as many push URLs as you want for a single remote, but keep in mind that this will affect all the branches that use that remote as their upstream. If you want more fine-grained control over which branches go to which remotes, you can use the next method.
Creating Separate Branches
Another way to push your code to two remotes is to create separate branches for each remote and set their upstreams accordingly. For example, if you have a branch called master that you want to push to your main repository, and another branch called deployment that you want to push to your deployment repository, you can do something like this:
# create the deployment branch from master
git checkout -b deployment master
# add the deployment remote
git remote add deployment git://another/repo.git
# set the upstream for the deployment branch
git push --set-upstream deployment deployment
This will create a new branch called deployment that tracks the deployment remote, and push it there. Now, whenever you want to update your deployment repository, you can simply run git push from the deployment branch.
You can also merge changes from your master branch into your deployment branch before pushing, or use rebase or cherry-pick if you prefer. The advantage of this method is that you can have different histories and configurations for each remote.
Conclusion
In this post, I showed you two ways to push your code to two remotes using git: adding multiple push URLs for a single remote, or creating separate branches for each remote. Both methods have their pros and cons, so choose the one that suits your workflow best.
I hope you found this post useful and learned something new.