Code scanning filters doesn't offer a drop down to filter by PR

[jsoref]

Select Topic Area

Product Feedback

Body

My tooling often generates code scanning alerts to PRs as opposed to branches.

Code scanning results has a report page:

There's a link that says:
View all branch alerts.

But, it isn't actually a link to a branch filter.

Instead, it's to a pr:1 tool:check-spelling is:open filter:

That filter is wonderful. But if you visit https://github.com/check-spelling-sandbox/opentelemetry-collector-contrib/security/code-scanning directly, you'd never be able to generate that link on your own using the ui:

default search: is:open branch:placeholder (note that clicking the field actually leaves you with a blank field, not the visible default query which is problematic).

That includes this text:

Security icon
This branch hasn't been scanned yet.
For more information about code scanning, see here.

If check-spelling were run against the product that produced this page, it would say:

Do not use (click) here links

For more information, see:

• https://www.w3.org/QA/Tips/noClickHere
• https://webaim.org/techniques/hypertext/link_text
• https://granicus.com/blog/why-click-here-links-are-bad/
• https://heyoka.medium.com/dont-use-click-here-f32f445d1021

(?i)(?:>|\[)(?:(?:click |)here|link|(?:read |)more)(?:</|\]\()

Anyway, there's a language filter:

There's a tool filter:

There's a branch filter (as demonstrated by the default search):

There's a rule filter:

There's a severity filter:

There's a sort thing:

And the open/closed items at the beginning also act as filters.

The branch filter is actually not solely a branch filter as it also offers filtering on tags. It's the logical place to put the PR list to allow filtering by PR. Especially given that filtering by PR is more or less mutually exclusive to filtering by Branch or Tag.

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