GitKraken won't push to new remote ("Select remote branch to push/pull with 'master': ")

Question

So I've create a new repo on remote, and managed to connect it (I belief) to client (Git Kraken). Now it want a branch name from me for a repo that doesn't have any. Note that its also ...push/pull with "master":, that is master with a colon. Pretty much explaining a mechanic that is at play here is as welcome as actually drawing out steps.

open your repo in bitbucket website and follow the instuction in '"Get your local Git repository on Bitbucket' — San Daniel, Feb 21 '19 at 06:12

Masoud Azizpour · Accepted Answer · 2017-05-15T11:17:46.420

53

You'd need to "Set Upstream" for your local branch. To do so:

Find your local branch on left pane under LOCAL,
right-click and select "Set Upstream",
name your new remote branch on the prompt and click "Submit",
click "Push" on the top toolbar.

To avoid confusion, you could also name your local branch (to keep it the same as the remote) at the time of creating the branch from master or whichever remote you want to branch from.

Note: Though there shouldn't be drastic differences between versions, the above is based on GitKraken 2.5.0 64-bit (non-pro version)

edited May 15 '17 at 11:17

answered May 15 '17 at 10:53

Masoud Azizpour

546
5
4

Sounds right. I don't remember how i've solved this. – janat08 May 15 '17 at 20:46
My GitGraken v3.02 (free) does not have the option to "Set Upstream." BTW GitHub Desktop v1.03 (free) has a "Publish" option that solves this problem. – peterdcasey Oct 02 '17 at 05:57
Right, but It is a very bad operation experience – Rwing Jun 17 '19 at 10:58
This doesn't work for me. – Dan Nissenbaum Jan 11 '23 at 07:23

score 1 · Answer 2 · answered Jul 22 '16 at 13:51

1

I had this same problem - I typed in "origin/master" and that pushed it for me, I guess it just wants to know where it is pushing it to even if there is only one place.

answered Jul 22 '16 at 13:51

charliethegoldfish

33
6

that wouldn't work for me, maybe since it was an empty repository. – janat08 Jul 24 '16 at 01:31

score 1 · Answer 3 · answered Aug 14 '16 at 18:31

If you have connected to a "Remote" successfully and you see it in your list under remotes. what ever name you gave it there is what you need to type in when you see that message. So for the example below you can type origin/master but only because when setting up the remote I called it origin.

score 0 · Answer 4 · answered Jan 01 '18 at 14:57

0

When setting upstream, include the /master like this.

"whatever-repo-name/master"

This worked for me.

answered Jan 01 '18 at 14:57

ellaRT

1,346
2
16
39

score 0 · Answer 5 · answered Jan 15 '21 at 13:31

0

None of these options worked for me,

For me, the problem was not with GitKraken itself but with a particular repository.

What ultimately resolved this problem was creating a new one.

I believe the error occurred as I renamed the repository.

answered Jan 15 '21 at 13:31

Alejandro Soumah

11
2

GitKraken won't push to new remote ("Select remote branch to push/pull with 'master': ")

5 Answers5