3 ms·

I once tried to PR from hub. It sent the PR from my branch on my fork to master on my fork. Obviously I wished to PR against the original thing I forked from.

• emacsfodder 11y ago
  What you needed was to use the options -h (head, ie. the feature branch) and -b (base, ie the upstream master) eg. git pull-request \ -m "I added an awesome feature"\ -b baserepo:master\ -h myfork:feature-branch
  • justinsb 11y ago
    The GitHub web interface defaults to the PR-to-upstream behavior though, so this is at least an inconsistency; I would argue it is a bug.
• ultrafez 11y ago
  You could submit a pull request to hub to fix it! Perhaps not using hub to do so, though.
  • emacsfodder 11y ago
    hub works just fine to create a PR, some lack of RTFM is at play.
    • skj 11y ago
      So, I never trust users to give me advice on features to add. But I always believe them when they say something is difficult or confusing. Research should not be required to make a good CLI do what you want, provided you understand what you want.
      • Manishearth 11y ago
        Might like http://blog.codinghorror.com/listen-to-your-community-but-dont-let-them-tell-you-what-to-do/ http://blog.codinghorror.com/listen-to-your-community-but-do...
• michaelmior 11y ago
  I believe will always default to sending the PR to the remote named origin. If you have the original repo listed as origin and your repo as a remote with your username, you get the expected behaviour. I think the issue here is that hub has no explicit knowledge of the ancestry of the repo so unless it fetches this from the GH API, I think it's doing the only logical thing.
• mgold 11y ago
  It sure would be nice to have `--dry-run --verbose` to see exactly what it's going to do.