-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
1d6ee20
commit f3ed426
Showing
1 changed file
with
15 additions
and
24 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,38 +1,29 @@ | ||
| #### What does this PR do? | ||
|
|
||
| Describe the overall purpose of the PR changes. Doesn't need to be as specific as the | ||
| individual commits. | ||
|
|
||
| #### Helpful background context | ||
|
|
||
| Describe any additional context beyond what the PR accomplishes if it is likely | ||
| to be useful to a reviewer. | ||
|
|
||
| Delete this section if it isn't applicable to the PR. | ||
|
|
||
| #### How can a reviewer manually see the effects of these changes? | ||
| ### Purpose and background context | ||
| Describe the overall purpose of the PR changes and any useful background context. | ||
|
|
||
| ### How can a reviewer manually see the effects of these changes? | ||
| Explain how to see the proposed changes in the application if possible. | ||
|
|
||
| Delete this section if it isn't applicable to the PR. | ||
|
|
||
| #### Includes new or updated dependencies? | ||
|
|
||
| ### Includes new or updated dependencies? | ||
| YES | NO | ||
|
|
||
| #### What are the relevant tickets? | ||
|
|
||
| Include links to Jira Software and/or Jira Service Management tickets here. | ||
| ### Changes expectations for external applications? | ||
| YES | NO | ||
|
|
||
| #### Developer checklist | ||
| ### What are the relevant tickets? | ||
| - Include links to Jira Software and/or Jira Service Management tickets here. | ||
|
|
||
| ### Developer | ||
| - [ ] All new ENV is documented in README | ||
| - [ ] All new ENV has been added to staging and production environments | ||
| - [ ] All related Jira tickets are linked in commit message(s) | ||
| - [ ] Stakeholder approval has been confirmed (or is not needed) | ||
|
|
||
| #### Code reviewer checklist | ||
|
|
||
| - [ ] The commit message is clear and follows our guidelines (not just this pull request message) | ||
| ### Code Reviewer(s) | ||
| - [ ] The commit message is clear and follows our guidelines (not just this PR message) | ||
| - [ ] There are appropriate tests covering any new functionality | ||
| - [ ] The documentation has been updated or is unnecessary | ||
| - [ ] The changes have been verified | ||
| - [ ] The provided documentation is sufficient for understanding any new functionality introduced | ||
| - [ ] Any manual tests have been performed or provided examples verified | ||
| - [ ] New dependencies are appropriate or there were no changes |