Push to multiple remotes

53 votes

We have the need to push our code to both Github enterprise and Azure Devops it would be great if there was a way to tell GitKraken to push to both locations rather than having to "push, set upstream, push again, set upstream back."

Under consideration Suggested by: Jeremy (01 Oct, '21) • Upvoted: 21 Apr • Comments: 9

Comments: 9

01 Oct, '21
alex.latham@gitkraken.com Admin
Hi Jeremy,

I went ahead and approved this request since there is no way to simultaneously push to multiple remotes at the same time in GitKraken. However, you do not need to change the upstream each time you push. Instead, you can leverage drag-and-drop functionality to push to a remote without touching your upstream setting. Check out the .gif on this page: https://support.gitkraken.com/working-with-repositories/pushing-and-pulling/#drag-and-drop-to-push
16 Dec, '21
John
This would be extremely useful to me
29 Dec, '21
doug
I actually just submitted a support ticket about this and was also pointed to this site as well as being told about the drag and drop.

I just want to mention this totally works on the command line -- even within the command line client on GitKraken. Just use

git remote set-url --add --push origin /path/to/repo1
git remote set-url --add --push origin /path/to/repo2

to set the remotes up (would be nice to have GUI support for multiple push locations as well, but that's less important to me as it's just configuration)

You can verify your remotes with

git remote -v

to see that repo1 and repo2 are both set as your push locations for origin and then just git push and voila.

Seems like GitKraken GUI only uses the last push entry in git remote -v to push. It ignores any others that are set.
18 May, '22
Francis
The drag-and-drop approach is not viable when the sidebar has like 500+ branches in it. This functionality needs to be worked on.
1
16 Jul, '22
Josh
As Franics says this workaround does not function with tons of branches from say a very old large open source code base.

The reason I got gitkraken pro was to work with many private repos (as a contractor). I have my main private repo and ideally could have a setting such that branches under a directory (COMPANY1/branch1, COMPANY2/branch1) can only be pushed into one remote without triple confirm.

IE the Push button asks where to push it (my private repo, or my client's repo)
27 Jan, '23
mmebsout
Also when a new branch is pushed to origin I can't push it to the secondary remote. I have to create the new branch in the remote via the command line.
14 Apr, '23
Susan Conger
Where is this at? Can we push to multiple remote repositories inside GitKracken?
27 Feb
Jason
Is there any update on this feature request? Some 2+ years later.

This is a real blocker for those of us required to use multiple remotes for the same code base. Using profiles within GitKraken is a hack and cumbersome.

Any update would be appreciated.
21 Mar
kriboogh
What would be handy is you right click on a branch (local) > context menu "Push" > submenu lists remotes and "push to all" (same behaviour as pushing tags)