Skip to content

chore: add customer impact statements #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ben-wilson-peak wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: add customer impact statements #22

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 16 additions & 9 deletions PULL_REQUEST_TEMPLATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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

<!---
Expand Down