Repository navigation
Pull requests view in a fork only lists the fork's PRs since the latest nightly #35166
Description
What happens
In a project whose origin is a fork (origin = TonybynMp4/t3code, upstream = pingdotgg/t3code), the Pull requests view on the latest nightly lists only PRs opened against the fork. My PRs against pingdotgg/t3code no longer appear, even though they're the ones I work on daily.
On the previous nightly the same view, with the same 4 filters, listed my upstream PRs (#34662, #34638, #29705, ...) with pingdotgg/t3code shown as the repo on each row. Now it shows six old fork PRs (#11 to #19) with TonybynMp4/t3code as the repo, and nothing from upstream.
There's no way to get the upstream list back from the UI. Filters has no repository option, so a fork user can't reach the PRs that matter.
Suggestion
Either of these would fix it:
- List PRs from every repo the project knows about (origin and upstream) in one list. Each row already shows its repo, so mixing them reads fine.
- Add a repository selector to the Filters menu, defaulting to the parent repo when the project is a fork, since that's where PRs from a fork get opened.
I'd lean toward option 1 with option 2 as the filter on top, so nothing is hidden by default.
Screenshots
| Previous nightly | Latest nightly |
|---|---|
 |
 |
Activity
TonybynMp4 commentedon Nov 12, 2026
Linking PRs to a thread hits the same thing. I linked upstream PR #35173 and the thread's Pull requests panel shows it as
#35173 tonybynmp4/t3codewithgithubproxy.fjygbaifeng.eu.org/tonybynmp4/t3codeunderneath, with no title, state, or diff stats. It looks like the number got resolved against the fork instead ofpingdotgg/t3code. #15387 in the same panel was linked earlier and still shows correctly asping…t3code.