Implicit AND differs from explicit AND for is:issue is:merged on Issues page

[Galuisss]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Code Search and Navigation

Body

On the repository Issues page, the filter is:issue is:merged appears to return merged pull requests.

I would expect this query to return no results, because is:issue should exclude pull requests, and is:merged only applies to pull requests.

However:

• is:issue is:merged returns merged PRs.
• is:issue AND is:merged returns no results, as expected.

According to GitHub's search documentation, spaces between search terms should be treated as implicit AND, so these two queries should be equivalent.

This looks like implicit AND and explicit AND are handled differently for this combination of qualifiers on the Issues page.

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