From f10b4d82855ba961ae7ba773f39ee7945bed669b Mon Sep 17 00:00:00 2001
From: Erin Song <121973038+erinysong@users.noreply.github.com>
Date: Thu, 3 Oct 2024 10:33:45 -0700
Subject: [PATCH] Create code review guide

---
 .github/pull_request_template.md  | 2 +-
 docs/dev-practices/code_review.md | 6 ++++++
 2 files changed, 7 insertions(+), 1 deletion(-)
 create mode 100644 docs/dev-practices/code_review.md

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index dec0b9fac..4f2349204 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,6 +1,6 @@
 ## Ticket
 
-Resolves #00
+Resolves #001
 <!--Reminder, when a code change is made that is user facing, beyond content updates, then the following are required:
 - a developer approves the PR
 - a designer approves the PR or checks off all relevant items in this checklist.
diff --git a/docs/dev-practices/code_review.md b/docs/dev-practices/code_review.md
new file mode 100644
index 000000000..56d4db394
--- /dev/null
+++ b/docs/dev-practices/code_review.md
@@ -0,0 +1,6 @@
+# Code Review
+
+After creating a pull request, pull request submitters should:
+- Add at least 2 developers as PR reviewers (only 1 will need to approve)
+- Message on Slack or in standup to notify the team that a PR is ready for review
+- If any model was updated to modify/add/delete columns, run makemigrations and commit the associated migrations file.
\ No newline at end of file