2x1=10

When work­ing on a project on GitHub, I some­times like to keep an addi­tion­al copy float­ing around on my own serv­er for eso­ter­i­cal rea­sons. While the fol­low­ing is pos­si­ble:

$ git remote add origin git@a.b:c/d.git
$ git remote add another git@w.x:y/z.git

$ git push origin
$ git push another

it is quite annoy­ing to issue the push com­mand twice — advanced git-fu to the resuce. Some dude over at Stack Over­flow point­ed out that Git sup­ports the notion of a pushurl, being an end­point for push­ing to a giv­en remote. The fun thing is that every remote may have mul­ti­ple push URLs, which is exact­ly what I need­ed.

It needs to be said that despite the usage of the --add flag in the fol­low­ing snip­pet, a push URL always over­writes the default URL, so adding only one URL results in the orig­i­nal entry being over­ruled. So, for the sit­u­a­tion giv­en in the exam­ple above:

$ git remote add origin git@a.b:c/d.git
$ git remote set-url --add --push origin git@a.b:c/d.git
$ git remote set-url --add --push origin git@w.x:y/z.git

$ git push origin

And that’s it. By push­ing to origin Git instead push­es to both reg­is­tered URLs.