Replies: 1 comment
-
|
I’m seeing the same issue and I agree with your assessment. A draft PR is still fundamentally an open PR, so excluding drafts from the default Open view breaks the expectation that “Open” shows everything that is currently open. As you mentioned, all other filters work by reducing the existing result set, but the Draft filter behaves differently by effectively acting as a separate top-level category. This was confusing in practice , I initially thought my PRs hadn’t opened correctly because they weren’t visible in the Pull Requests view. That kind of uncertainty suggests the UX isn’t matching user expectations. Your suggestion feels more consistent with the existing model:
That approach would restore consistency with other filters and reduce confusion, especially in the mobile UI. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Other exclusive filters live in the first dropdown (current Open).
A draft PR is always open, because otherwise it is closed or merged (meaning it had to leave draft to become merged). The behavior of all filters (except this one) is to reduce the set of items you see from the default state. However, the draft filter behaves completely differently because we are now excluding drafts from open PRs and showing open drafts separately, as if it were a separate top level data source.
Impact: I actually thought something was wrong or that my PRs never opened because they weren't visible in my pull requests.
Suggestion:
Open.ℹ️ Additional Debug Info
GitHub for iOS, Version 1.242.0 (183428589) Device: iPhone18,2 (iOS 26.1)Beta Was this translation helpful? Give feedback.
All reactions