> The PR is in the upstream repository:
https://github.com/foliojs/restructure
> not in my fork
>
> BTW: this the recommended approach when collaborating with third party
> projects in github: create a fork, push to your fork and create a PR in the
> upstream repository.
>
> Even if the PR was created by me, it would not show because is looking to
> my repository and not to the upstream
Please give 23.1 build 20075 a try: Help|Check for Latest Build. It will now query:
is:pr is:open repo:blikblum/restructure repo:foliojs/restructure involves:blikblum
and thus give you pull request #51. Note that it will still filter out all pull requests which do not either target blikblum/restructure or originate from blikblum/restructure, i.e. you will not see all pull requests from repo:foliojs/restructure which are assigned to you (or which you have authored). There would be no appropriate branch anchor in blikblum/restructure for such pull requests.
The Log window behaves different: it will send a separate query for every remote. Hence, if you have remotes "origin" (blikblum/restructure) and "upstream" (repo:foliojs/restructure), you will see all pull requests.
> I understand the reasoning. I'm not requesting to be the default behavior,
> i am requesting is a escape hatch to fetch arbitrary PR (i can be somewhat
> hidden in context menu or as a small button like Log window). It not need
> to be in My history. can be in All branches
>
> I collaborate to many open source projects, and in most of them i am not a
> maintainer so i cannot set myself as a reviewer.
>
> Many times, i am interested in checking third party PRs to test and give my
> opinion
Please request this at UserEcho:
https://smartgit.userecho.com/
> --
> You received this message because you are subscribed to the Google Groups
> "SmartGit" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
>
smartgit+u...@googlegroups.com.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/smartgit/CA%2BnZ%3DyNv2pOfdF7ERF%2BLytvwjSTfmRKy4aPyhPnhtU_w6nvKww%40mail.gmail.com.
>