💬 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. ⭐

Hello

Individual repository pull request tabs currently lack the native saved views functionality available for issues. While teams can save up to 25 shared filters in the repository issues sidebar, the pull requests sidebar does not support saving custom views. This forces code reviewers to waste time manually re-typing complex query strings every day to track repository-specific milestones, team labels, or authors.

To resolve this limitation, platforms should extend the repository-level saved views architecture directly into repository pull request tabs. To keep the interface organized, the system should automatically filter search parameters and only surface views containing explicit pull request qualifiers. Saved views meant strictly for standard issues should remain locked inside the issues tab to prevent cross-contamination.

Implementing this update will create perfect parity between issue and pull request workflows. It will accelerate daily team code reviews by removing the dependency on scattered browser bookmarks and eliminating the constant frustration of entering repetitive search keywords.

Regards