Make PR list sort order & filters configurable

[jml6m]

Select Topic Area

Product Feedback

Body

On the repository Pull requests tab, I frequently want the list sorted by Recently updated (updated descending). Today, while GitHub supports sorting via the UI and the URL is updated to reflect the chosen sort, it’s not possible (as far as I can tell) to set a default sort for the PR list that persists without relying on:

• bookmarking a pre-filtered URL, or
• manually editing/formatting the query in the URL each time.

This makes a common workflow feel “hidden” behind URL/query mechanics rather than being a first-class preference in the UI.

Why it matters / use cases

• Triage and review workflows are often driven by “what changed most recently?”
• When switching between repositories frequently, repeatedly re-setting the sort order adds friction.
• Newer users may never discover URL-based sorting/search qualifiers, even though they exist.

Requested enhancement

Add a built-in UI option to persist PR list view preferences, such as:

• Default sort order for Pull Requests (e.g., Recently updated)
• Potentially other PR list preferences (open/closed defaults, or last-used filters), ideally per-repo or per-user.

Examples of acceptable UX:

• “Set as default” next to the Sort dropdown
• A small preferences entry for the Pull requests tab (“Default sort: Recently updated”)
• Remember last-used sort/filter per repo (like “sticky” state)

Current behavior / workaround

GitHub supports sorting and filtering the PR list, and the URL reflects the selected view (which makes it shareable), but persisting it requires using that URL again later rather than a UI-backed default.

Additional context

This is specifically about the Pull requests list page (repo tab), not sorting within an individual PR.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[timdiggins]

Totally agree with this, but think this is a dupe (though limited to PRs) of https://github.com/orgs/community/discussions/16154