Can I push and pull without explicit branch specifying?

Question

I do not want to type git branch --set-upstream-to=origin/<branch> myBranchName.

I tried

[push]
    default = current

but it works only for push, not for pull, [pull] do nothing.

Also tried

[branch]
    autosetupmerge = always
    autosetuprebase = always

My git version is 2.35 (current stable in Gentoo) so push.autoSetupRemote is unavailable for me. Only custom aliases, no simple config option?

Does this answer your question? [Git alias on current branch](https://stackoverflow.com/questions/15112280/git-alias-on-current-branch) — evolutionxbox, Jul 21 '22 at 09:06
Why don't you want to type `git branch --set-upstream-to=origin/ myBranchName`? Would it not solve your problem? — mkrieger1, Jul 21 '22 at 09:21
Upstreams are overrated. I never use them. I never say `pull` either. I have a feeling this is an xy question and you should really be questioning your working habits. — matt, Jul 21 '22 at 13:34

tymtam · Answer 1 · 2022-07-21T12:30:59.117

0

I'm on an ancient 2.24 and use push.default=current in my config.

[push]
        default = current

Also, even without this you don't need to type the set-upstream command. git push should type it for you and then you can just copy/paste it.

For example:

❯ git push
fatal: The current branch feature/test has no upstream branch.
To push the current branch and set the remote as upstream, use

    git push --set-upstream origin feature/test

(select and right click here)
❯  git push --set-upstream origin feature/tm/test

edited Jul 21 '22 at 12:30

answered Jul 21 '22 at 12:24

tymtam

31,798
8
86
126

But this config is only for push, not pull. – Vitaly Zdanevich Jul 21 '22 at 13:20
Once you push this branch you're repo will have the link stored in `.git/config` – tymtam Jul 21 '22 at 13:22
But I want to pull and push without `--set-upstream` for every new branch - is that possible? – Vitaly Zdanevich Aug 12 '22 at 17:30
Yes, that's what `push.default=current` does. The rest of my answer is just to say that even if you don't have the setting you don't need to type you just copy/paste. But if you have the setting you don't need copy/paste. – tymtam Aug 13 '22 at 06:18
I have `[push] default = current` in my global git config but still cannot `git pull` on new branch without additional something :( – Vitaly Zdanevich Aug 14 '22 at 11:21
I don't understand now. When you say you cannot `git pull`, what do you mean? Normally you can `git pull` and then `git checkout branch_name` – tymtam Aug 15 '22 at 00:37
I can `git pull -u origin branchname`, but I want `git pull` – Vitaly Zdanevich Aug 15 '22 at 07:26
`git pull` doesn't have `-u` option :/ – tymtam Aug 15 '22 at 12:28
Ops I mean `git pull origin branchname` – Vitaly Zdanevich Aug 16 '22 at 06:53

score 0 · Accepted Answer · answered Jan 13 '23 at 16:29

branch.autosetupmerge=always is almost certainly not what you want; it will cause all new branches you create to use their source as the upstream - even if you branch from another local branch.

As of git 2.37+, you probably want to set these two things:

git config --global branch.autoSetupMerge simple: This will set up the upstream automatically, but only if the new local branch name matches the remote branch name.

git config --global push.autoSetupRemote true: This will automatically set up tracking when you push new branches - it also makes git push "just work" for new branches.

Can I push and pull without explicit branch specifying?

2 Answers2