Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Feature request: Make 'origin' remote name configurable. #720

Open
elmart opened this issue Dec 3, 2014 · 7 comments
Open

Feature request: Make 'origin' remote name configurable. #720

elmart opened this issue Dec 3, 2014 · 7 comments
Labels
config feature

Comments

@elmart
Copy link

elmart commented Dec 3, 2014

At some places, like hub create, an origin remote name is used by default.
I like using upstream instead of origin.
So, it would be nice for such default remote name to be configurable somewhere.
Thanks, and keep up your hard work. hub rocks!
@augmentedfourth augmentedfourth mentioned this issue Dec 16, 2014
Closed
@mislav mislav added the feature label Dec 23, 2014
@yegle yegle mentioned this issue Jan 4, 2015
Closed
@mislav mislav added the config label Sep 27, 2015
@mislav
Copy link
Owner

mislav commented Sep 27, 2015

Thanks for the suggestion! This is an often-requested feature. We'll see if we can make it configurable.

@DXist
Copy link

DXist commented Jan 22, 2016

+1. Also prefer to use upstream remote for upstream and origin for my fork.

Use following git alias to switch to this setup:

switchorigin = !git remote add upstream $(git config --get remote.origin.url) && git fetch upstream && git checkout master && git branch --set-upstream-to upstream/master && git remote -v rm origin && git remote -v add origin

@mislav mislav mentioned this issue Aug 17, 2016
Closed
38 tasks
@vermiculus vermiculus mentioned this issue Sep 17, 2016
Open
vermiculus added a commit to vermiculus/magithub that referenced this issue Sep 17, 2016
@vermiculus
Protect against non-GitHub repositories
471f764 
I haven't found a way to ban the popups via predicate, but the functions
themselves will now error-out when the current repository's "origin"
remote does not point to GitHub.

It would be possible to use `magit-get-upstream-remote' instead, but hub
isn't smart enough for that yet -- it assumes "origin".

See also mislav/hub#720.
@rcorre
Copy link

rcorre commented Aug 5, 2017

Any plans for this? If you are a contributor working on a fork, hub issues is useless, since all the issues are on upstream, not origin.

@mislav
Copy link
Owner

mislav commented Aug 8, 2017

@rcorre Which version of hub are you using? If you're using hub issue command, you should be using the latest prerelease version because that command is greatly improved there. Also, hub will automatically pick the upstream remote over the origin remote as the "canonical" repo of where issues should be fetched from.

@rcorre
Copy link

rcorre commented Aug 8, 2017

@mislav yes, looks like that works. thanks!

@massich
Copy link

massich commented May 17, 2019

What if we want to use a different name than upstream or origin. Like the org's name or the username. What's the status? and how could I configure it? I did not find it in the doc.

@massich
Copy link

massich commented May 17, 2019 •
edited
Loading

Is there a newer related issue to cross-reference with this one? #1973 (actually I've commented on it already)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
config feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@mislav @elmart @DXist @rcorre @massich