From 0c7759869d4ccd0d16a0e9dc0f29ff5d197365ff Mon Sep 17 00:00:00 2001
From: ben-wilson-peak <117664255+ben-wilson-peak@users.noreply.github.com>
Date: Fri, 8 Mar 2024 15:07:15 +0000
Subject: [PATCH] chore: add customer impact statements

---
 PULL_REQUEST_TEMPLATE.md | 25 ++++++++++++++++---------
 1 file changed, 16 insertions(+), 9 deletions(-)

diff --git a/PULL_REQUEST_TEMPLATE.md b/PULL_REQUEST_TEMPLATE.md
index 0a1dbf8..e129320 100644
--- a/PULL_REQUEST_TEMPLATE.md
+++ b/PULL_REQUEST_TEMPLATE.md
@@ -24,18 +24,12 @@ Put an `x` in all that apply and explain why in any that don't
 - [ ] 📄 The documentation is up-to-date
 - [ ] 🔐 The security considerations section in the PR description is complete - **Please do not remove this**
 
-## Dependencies
+## Customer Impact
 
-<!---
-Add links to any pull requests or documentation related to this pull request.
--->
-
-- [YOUR LINK HERE](https://example.com/)
-
-**Does this PR introduce a breaking change?** 
+**Can this change have a customer impact?** 
 
 <!---
-(What changes might users need to make in their application due to this PR?)
+(Could this impact a customer at all?)
 -->
 
 - [ ] Yes
@@ -45,6 +39,19 @@ Add links to any pull requests or documentation related to this pull request.
 **If you answered yes, then please explain below.**
 -->
 
+<!---
+Examples:
+
+- Customer will have to change XYZ API call
+  - We've considered backwards compatible changes but were unable to accomodate (link to conversation)
+  - Communication has been planned
+- The button has moved
+  - The average user shouldn't have a problem finding the new button
+- The change may cause downtime
+  - We have scheduled a maintenance window for deployment
+  - Maintenance window has been communicated with potentially impacted customers
+-->
+
 ## Security Considerations
 
 <!---