ci-status doesn't work with multiple remotes

[danielcompton]

If I have a project with two remotes, upstream and origin, running hub ci-status <sha> will only check the upstream remote. If I rename upstream to apstream then hub appears to check origin and returns a correct ci-status command. It seems like there might be an ordering issue here? I'm not sure whether hub should check multiple remotes or not for this.

$ hub ci-status
pending
$ hub remote add upstream juxt/edge
$ hub ci-status
no status
$ hub remote
origin
upstream
$ hub remote rm upstream
$ hub remote add apstream juxt/edge
$ hub ci-status
pending
$ hub remote
apstream
origin

[mislav]

Hub commands like ci-status have to guess which one of the git remotes points to the "canonical" version of the repository from which things like issues, PRs, Status API etc will be read. The upstream remote always has precedence over origin remote. This is what our users expect by now.

If you wish to specify explicitly which remote should be used, this is not yet possible, but planned for next big release in the form of global --remote flag that can be specified for any hub command where it's applicable.

[eranation]

any updates on that --remote flag? :) if I follow the instructions on https://hub.github.com/ since forking using these instructions sets your fork as the origin and the original repo as upstream, the ci-status will always show nothing.

[mislav]

@eranation Whoa, thanks for pointing that out. Reopening while I investigate