diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 0cf87b2fa1..7dc7652e5f 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -13,6 +13,34 @@ Fixes #replace_this_text_with_the_issue_number
-
-
+
CodeQL Alerts
+
+
+After the PR has been submitted and the resulting GitHub actions/checks have been completed, developers should check the PR for CodeQL alert annotations.
+
+
+Check the PR's comments. If present on your PR, the CodeQL alert looks similar as shown
+
+![Screenshot 2024-10-28 154514](https://github.com/user-attachments/assets/ea66c586-c14c-45fd-8705-1c116224e704)
+
+
+
+
+Please let us know that you have checked for CodeQL alerts. **Please do not dismiss alerts.**
+- [ ] I have checked this PR for CodeQL alerts and none were found.
+- [ ] I found CodeQL alert(s), and (select one):
+ - [ ] I have resolved the CodeQL alert(s) as noted
+ - [ ] I believe the CodeQL alert(s) is a false positive (Merge Team will evaluate)
+ - [ ] I have followed the Instructions below, but I am still stuck (Merge Team will evaluate)
+
+Instructions for resolving CodeQL alerts
+
+If CodeQL alert/annotations appear, refer to [How to Resolve CodeQL alerts](https://github.com/hackforla/website/issues/6463#issuecomment-2002573270).
+
+In general, CodeQL alerts should be resolved prior to PR reviews and merging
+
+
+
### Screenshots of Proposed Changes To The Website (if any, please do not include screenshots of code changes)