gh pr view cannot find open pull requests #888

Activity

1. maxandersen

   added

   bugSomething isn't workingSomething isn't working

   on May 8, 2020
2. mislav commented on May 8, 2020

   

   mislav

   on May 8, 2020

   Last edited by mislav

   Contributor

   More actions

   Thank you for reporting! I cannot reproduce right now because your PR got merged in the meantime and is no longer open.

   Additionally, I have checked out a fork PR in a different repository that has the base branch set to develop and gh pr view worked there, so no luck reproducing either.

   The next time you can reproduce with an open source repository, can you give us a heads up and also include your git remote -v configuration and more information about the current branch (git config --get-regexp branch.`git branch --show-current`.*)?
3. mislav

   added

   more-info-neededMore info needed from user/contributorMore info needed from user/contributor

   on May 8, 2020
4. maxandersen commented on May 8, 2020

   

   maxandersen

   on May 8, 2020

   Author

   More actions

   okey, here is a new PR with same issue: quarkusio/quarkusio.github.io#541

   git remote -v
   maxandersen      https://github.com/maxandersen/quarkusio.github.io.git (fetch)
   maxandersen     https://github.com/maxandersen/quarkusio.github.io.git (push)
   origin  https://github.com/quarkusio/quarkusio.github.io (fetch)
   origin  https://github.com/quarkusio/quarkusio.github.io (push)
   xorye   https://github.com/xorye/quarkusio.github.io.git (fetch)
   xorye   https://github.com/xorye/quarkusio.github.io.git (push)
   

   git config --get-regexp branch.`git branch --show-current`.*

   returns nothing.
5. mislav commented on May 8, 2020

   

   mislav

   on May 8, 2020

   Contributor

   More actions

   git config --get-regexp branch.`git branch --show-current`.*

   returns nothing.

   Ah, thank you for this. The missing upstream configuration for a branch reminded me that we do have an issue for this open, although around gh pr status. These commands use the same mechanism for detecting the current branch.

   Duplicate of #575

   In the meantime, you can work around this by always publishing your branch to your fork like this:

   # note the `-u` (`--set-upstream`) flag
   git push -u maxandersen HEAD

   👍React with 👍3Reacted by Max Rydahl Andersen, Gonzalo Serrano and Nathaniel Ruiz Nowell
6. mislav

   closed this as completedon May 8, 2020
7. NathanielRN commented on Dec 17, 2021

   

   NathanielRN

   on Dec 17, 2021

   More actions

   This is curious because if I do gh pr ready, or status on aws-observability/aws-otel-python#48 it finds the PR just fine. But if I do gh pr view it doesn't work until I do the git push -u fork fix you mention @mislav .

   Would your team consider changing the gh pr view behvaior to be similar to the ready or status command when searching for the PR so that we don't need a tracking upstream for our branches? 🙂

   🚀React with 🚀1Reacted by Gonzalo Serrano
8. mislav commented on Dec 20, 2021

   

   mislav

   on Dec 20, 2021

   Contributor

   More actions

   @NathanielRN Yes, that's exactly what we're tracking in the referenced issue. The remote branch should be detected regardless of tracking information or not. Additionally, you're right that different commands have different branch detection logic. We will try to consolidate that into unified detection.

   ❤️React with ❤️1Reacted by Nathaniel Ruiz Nowell
9. maxandersen commented on Mar 8, 2023

   

   maxandersen

   on Mar 8, 2023

   Author

   More actions

   In the meantime, you can work around this by always publishing your branch to your fork like this:

   some years later - gh pr view still fails to find pr for my branch even when using -u to mark upstream.

   Any way to improve/get it working?
10. mislav commented on Mar 8, 2023

    

    mislav

    on Mar 8, 2023

    Contributor

    More actions

    @maxandersen Sorry for the nuisance. You can try rerunning the command with GH_DEBUG=api to see underlying API requests, including which branch is gh trying to query for.

    Additional, you could share with us the output of:

    git config --get-regexp "^branch.$(git branch --show-current).(remote|merge)\$"
11. maxandersen commented on Mar 8, 2023

    

    maxandersen

    on Mar 8, 2023

    Author

    More actions

    output is:

    git config --get-regexp "^branch.$(git branch --show-current).(remote|merge)\$"
    branch.alpha5.remote maxandersen
    branch.alpha5.merge refs/heads/alpha5
    

    and GH_DEBUG API shows it queries maxandersen remote but my remote setup is:

     git remote -v
    maxandersen	https://github.com/maxandersen/quarkusio.github.io (fetch)
    maxandersen	https://github.com/maxandersen/quarkusio.github.io (push)
    origin	https://github.com/quarkusio/quarkusio.github.io.git (fetch)
    origin	https://github.com/quarkusio/quarkusio.github.io.git (push)
    

    and origin is where I would expect it to look for the pull-requests.
12. kingthorin

    added 2 commits that reference this issue on Mar 5, 2025

    auth tests: Set upstream branch earlier

    ...

    1419bfe

    auth tests: Set upstream branch earlier

    ...

    8a0f274
13. fire966911-art

    added a commit that references this issue on Jan 6, 2026

    Create MAKIN-911 PROACTIVE FIRE EMERGENCY RESPONED SYSTEMS

    ...

    c055854