Update PR template (#1235)

Author: jimmyfagan

.github/pull_request_template.md

@@ -7,24 +7,14 @@ This PR template is here to help ensure you're setup for success:
 **JIRA Ticket:**
 [BB2-XXXX](https://jira.cms.gov/browse/BB2-XXXX)
 
-
 ### What Does This PR Do?
+
 <!--
 Add detailed description & discussion of changes here.
-The contents of this section should be used as your commit message (unless you merge the PR via a merge commit, of course).
-
-Please follow standard Git commit message guidelines:
-* First line should be a capitalized, short (50 chars or less) summary.
-* The rest of the message should be in standard Markdown format, wrapped to 72 characters.
-* Describe your changes in imperative mood, e.g. "make xyzzy do frotz" instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy to do frotz", as if you are giving orders to the codebase to change its behavior.
-* List all relevant Jira issue keys, one per line at the end of the message, per: <https://confluence.atlassian.com/jirasoftwarecloud/processing-issues-with-smart-commits-788960027.html>.
-
-Reference: <https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project>.
 -->
 
-Replace me.
-
 ### What Should Reviewers Watch For?
+
 <!--
 Common items include:
 * Is this likely to address the goals expressed in the user story?
@@ -46,24 +36,25 @@ Have you fully verified and tested these changes? Is the acceptance criteria met
 
 ### What Security Implications Does This PR Have?
 
-Please indicate if this PR does any of the following:  
+Please indicate if this PR does any of the following:
 
 * Adds any new software dependencies
 * Modifies any security controls
 * Adds new transmission or storage of data
-* Any other changes that could possibly affect security? 
+* Any other changes that could possibly affect security?
 
-* [ ] Yes, one or more of the above security implications apply. This PR must not be merged without the ISSO or team security engineer's approval. 
+- [ ] Yes, one or more of the above security implications apply. This PR must not be merged without the ISSO or team
+  security engineer's approval.
 
-  
 ### Any Migrations?
 
 <!--
 Make sure to work with whoever is doing the deploy so they are aware of any migrations that may need to be run
 -->
 
 * [ ] Yes, there are migrations
-  * [ ] The migrations should be run PRIOR to the code being deployed
-  * [ ] The migrations should be run AFTER the code is deployed
-  * [ ] There is a more complicated migration plan (downtime, etc) <!-- Make sure to include the details of the plan below -->
+    * [ ] The migrations should be run PRIOR to the code being deployed
+    * [ ] The migrations should be run AFTER the code is deployed
+    * [ ] There is a more complicated migration plan (downtime,
+      etc) <!-- Make sure to include the details of the plan below -->
 * [ ] No migrations