Search for PRs in issues view returns no results

[mook-as]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Issues

Body

Searching for pull requests no longer returns any results:
https://github.com/issues?q=is%3Apr%20AND%20repo%3Aoctocat%2FSpoon-Knife

That repo should have some pull requests:
https://github.com/octocat/Spoon-Knife/pulls

Searching for issues still works fine:
https://github.com/issues?q=is%3Aissue%20AND%20repo%3Aoctocat%2FSpoon-Knife

(I'm mostly using that view to get a concise list of PRs across a selection of repos; obviously for a single repo the second view makes way more sense. The workaround is https://github.com/search?type=pullrequests but that produces a less compact view.)

This, I believe, happened within the last 48h or so; sorry I couldn't narrow this down more.

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

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

[OpenSourcePatents]

Can confirm this looks like a regression in the /issues unified search view.
The is:pr filter appears to have broken for that endpoint while is:issue still works, which points to a backend indexing or routing change on GitHub's side rather than anything in your query.
Your workaround via github.com/search?type=pullrequests is the right call for now.
Bookmarking that URL is the best option until GitHub fixes it.
Worth filing this as a bug via GitHub Support directly with your reproduction links so it gets to the right team, since community discussions don't always reach engineering.
There's no config change, setting tweak, or token adjustment that fixes a broken server-side search filter.

[thunze]

I've noticed similar behavior with the repo-specific issue search over the past few days (https://github.com/<org>/<repo>/issues?q=<something>).

I find the search across both issues and PRs to be particularly useful in huge repositories like nixpkgs to get a quick overview of the most recent events regarding a specific component. Now I have to search twice, once for issues and once for PRs.

[M393]

It's still working at https://github.com/microsoft/vscode/issues?q=sort%3Aupdated-desc, but not in other repositories.

[thunze]

Looks like it's now also fixed at https://github.com/NixOS/nixpkgs. Thanks!

[M393]

Seems to be fixed now.