Update filtering-and-searching-issues-and-pull-requests.md

[ko23]

Adding additional information about querying Pull Requests with is:merged and is:unmerged filters

Why:

Closes: #33906

What's being changed (if available, include any code snippets, screenshots, or gifs):

small but valuable update - only one line added
Filter issues by state of merging: is:merged or is:unmerged

it's a small but valuable update: adding is:merged and is:unmerged filters for Pull Requests queries
It can help with combining with other filters such as is:closed

Check off the following:

• I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

  • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

• For content changes, I have completed the self-review checklist.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md	fpt ghec ghes@ 3.13 3.12 3.11 3.10 3.9	fpt ghec ghes@ 3.13 3.12 3.11 3.10 3.9

---

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

[nguyenalex836]

@ko23 Thanks so much for opening a PR! ✨ I noticed you added the new line under

For issues, you can also use search to:

Do you think it might make more sense to add the new line under the following section, since the new line adds content relevant to PRs?

For pull requests, you can also use search to:

It would also make sense to update the line to read "Filter pull requests by state of merging..." (as it currently reads "Filter issues by state of merging..."

Let me know what you think! 💛

[ko23]

@nguyenalex836

• thank you for super-fast and valuable review
• "Do you think it might make more sense to add the new line under the following section, since the new line adds content relevant to PRs?" -> yes it can be good idea
• "It would also make sense to update the line to read "Filter pull requests by state of merging..." (as it currently reads "Filter issues by state of merging..." " -> ok, your proposal is better

Do you want to make changes by myself to this particular Pull Request or it should be done in other way?

[nguyenalex836]

@ko23 No problem at all! 💛 Feel free to make the changes yourself, and let me know whenever you are ready for me to review again!

[ko23]

@nguyenalex836

• I've just moved line to the Pull Request Section, as suggested (and I changed Filter issues to Filter Pull Requests
• I've also added link to About pull request merges for better navigation

[nguyenalex836]

@ko23 These changes look wonderful! I'll update the branch and get this merged once tests are passing 🍏

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡