Don't require GitHub repo to be origin remote

[parkr]

Hey, I have a repo I backup to GitHub so I have the github repo setup as the gh remote. It would be great if gh looped through all the remotes and found the one whose host matched the GITHUB_URL and used that for the relevant commands. Thoughts?

[owenthereal]

What gh commands are you trying to use this with?

[parkr]

gh browse, gh issue [create] both fail.

[owenthereal]

gh browse and gh issue only work with the origin remote. Do you mean gh takes an optional GitHub remote for the operation? Say gh browse gh where gh is pointing to another GitHub remote.

[parkr]

That's certainly an option. What I'd like is for gh to iterate through all the remotes and choose the best one. In the case that my remotes only contain one github.com remote, that choice should be easy as pie.

[deiga]

@parkr That sounds like an really expensive operation and way too error-prone. If your repo contains multiple github.com urls how do you think it should decide which is the one to use?

[parkr]

Based on who's logged in, I'd say. gh knows I'm logged in, so can choose git@github.com:parkr remotes. At the very least, giving me a way to specify a non-origin remote seems pretty reasonable. Ideally gh would know what repo to open and would open it.

[deiga]

@parkr what if you have write access to a remote which is not under your name? and you happen to have a fork of the same repo under your name?

[parkr]

@parkr what if you have write access to a remote which is not under your name? and you happen to have a fork of the same repo under your name?

hub always preferred the canonical repo. It would find the one under your username, check to see if it is a fork, and, if so then open up the canonical repo, otherwise open up my repo.

[cw-peter]

I'd like a --remote flag for gh issue as I'm often working with forks of the canonical repo which contains the issues

[flying-sheep]

yeah, indeed. same for gh pull-request.

for me, the canonical repo is seldomly origin, that’s my fork, unless i’m a contributor! i chose upstream as a personal convention, which coincidentally matches what other people do

[flying-sheep]

so, what names are supported now? gh? upstream? hub?

[owenthereal]

@flying-sheep The origin names lookup order is upstream, github and origin. Also gh has been merged into hub. Please move onto hub for further feature request.