From e0c81db07e8006ca27422a9e051943dbfb7f6efc Mon Sep 17 00:00:00 2001
From: sjalaleddine1 <91445581+sjalaleddine1@users.noreply.github.com>
Date: Fri, 30 Jun 2023 05:11:18 -0700
Subject: [PATCH] add(docs): adding PR tip from discourse form (#50650)

Co-authored-by: Mrugesh Mohapatra <1884376+raisedadead@users.noreply.github.com>
Co-authored-by: Krzysztof G. <60067306+gikf@users.noreply.github.com>
---
 docs/moderator-handbook.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/docs/moderator-handbook.md b/docs/moderator-handbook.md
index b3348caca5a..bde63ab5aa3 100644
--- a/docs/moderator-handbook.md
+++ b/docs/moderator-handbook.md
@@ -147,6 +147,12 @@ There are also situations where the contributor is trying to add a link to their
 
 You can close these invalid pull requests and reply to them with these [reply templates](reply-templates.md#closing-invalid-pull-requests).
 
+#### Filtering Pull Requests
+
+To sort Pull Requests for Quality Assurance for quick access to PRs that are ready for review, do not have a merge conflict, are not blocked, and have all status checks in green, use the following link to apply the filters:
+
+[Direct link with filter applied](https://github.com/freeCodeCamp/freeCodeCamp/pulls?q=is%3Aopen+is%3Apr+-label%3A%22status%3A+blocked%22+-label%3A%22status%3A+merge+conflict%22+status%3Asuccess+draft%3Afalse)
+
 #### Other Guidelines for Moderators on GitHub
 
 Though you will have write access to freeCodeCamp's repository, **you should never push code directly to freeCodeCamp repositories**. All code should enter freeCodeCamp's codebase in the form of a pull request from a fork of the repository.