Skip to content

Commit b7cfbec

Browse files
authored
Merge branch 'master' into task/NPA-5136/standardise-endpoint-errors
2 parents b0d1a39 + ada23d6 commit b7cfbec

File tree

1 file changed

+65
-33
lines changed

1 file changed

+65
-33
lines changed

.github/pull_request_template.md

Lines changed: 65 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -1,53 +1,85 @@
11
# Pull Request
22

3-
<!--
4-
Stages to complete before opening the Pull Request:
5-
- PR title should be formatted in the following structure `NPA-XXXXX: title abc`
6-
- Added yourself/others as Assignees
7-
- Added the correct labels
8-
- Add Jira ticket link in the Ticket Link section below
9-
-->
10-
11-
## Ticket Link
3+
## 🧾 Ticket Link
124

135
<!-- Add the Jira ticket link here -->
146

157
https://nhsd-jira.digital.nhs.uk/browse/NPA-XXXX
168

17-
## Description/Change Summary
9+
---
10+
11+
## 📝 PR Title Format
12+
13+
Must follow format: `NPA-XXXX: Short Description of the Change`
14+
15+
---
16+
17+
## 📄 Description/Summary of Changes
18+
19+
<!-- Describe the changes made in this PR. Include the purpose/scope/impact of the changes -->
20+
21+
- <!-- Add bullet points summarising key changes -->
22+
- <!-- Add bullet points summarising key changes -->
23+
- <!-- Add bullet points summarising key changes -->
24+
25+
---
26+
27+
## 🧪 Developer Testing Carried Out
28+
29+
<!-- Describe what tests (automated/unit/manual etc.) have been done for the ticket. Include: -->
30+
<!-- - Any tests added/updated -->
31+
<!-- - Evidence that each acceptance criterion from the Jira ticket is met -->
32+
33+
- [ ] <!-- Add bullet points for testing instructions -->
34+
- [ ] <!-- Add bullet points for testing instructions -->
35+
- [ ] <!-- Add bullet points for testing instructions -->
36+
37+
---
38+
39+
## 🧪 Reviewer Testing Required
40+
41+
<!-- Describe how to test the changes that have been made in the ticket. Include: -->
42+
<!-- - Testing environment details (e.g. sandbox/local setup) -->
43+
<!-- - Steps to verify the changes -->
44+
45+
- [ ] <!-- Add bullet points for testing instructions -->
46+
- [ ] <!-- Add bullet points for testing instructions -->
47+
- [ ] <!-- Add bullet points for testing instructions -->
48+
49+
---
1850

19-
<!-- Describe the changes made in this PR -->
51+
## ✅ Developer Checklist
2052

21-
-
22-
-
23-
-
53+
<!-- Complete before submitting the PR -->
2454

25-
## How to test?
55+
- [ ] PR title follows the format: `NPA-XXXX: <short-description>`
56+
- [ ] Branch name follows the convention: `<type>/NPA-XXXX-<short-description>`
57+
- [ ] Commit messages follow the template: `NPA-XXXX: <short-description>`
58+
- [ ] All acceptance criteria from the Jira ticket are addressed
59+
- [ ] Automated tests (unit/integration/API/infrastructure etc. tests) are added or updated
60+
- [ ] The [traceability matrix](https://nhsd-confluence.digital.nhs.uk/display/NPA/Traceability+matrix) is updated
61+
with
62+
new tests or requirements
63+
- [ ] Assignees and appropriate labels (e.g. `terraform`, `documentation`) are added
2664

27-
<!--- Describe in detail how you tested your changes -->
28-
<!--- Include details of your testing environment and the tests you ran to see how your change affects other areas of the code etc. -->
29-
<!--- Are there any automated tests that mean changes don't need to be manually changed? -->
65+
---
3066

31-
-
32-
-
33-
-
67+
## 👀 Reviewer Checklist
3468

35-
<!--
36-
Stages to complete before opening the Pull Request:
37-
- PR title should be formatted in the following structure `NPA-XXXXX: title abc`
38-
- Added yourself/others as Assignees
39-
-->
69+
<!-- To be completed by the reviewer -->
4070

41-
## Review Checklist
71+
- [ ] Changes meet the acceptance criteria of the Jira ticket
72+
- [ ] Code is able to be merged (no conflicts and adheres to coding standards)
73+
- [ ] Sufficient test evidence is provided (manual and/or automated)
74+
- [ ] Infrastructure/operational/build changes are validated (if applicable)
4275

43-
:information_source: This section is to be filled in by the **reviewer**.
76+
---
4477

45-
- [ ] I have reviewed the changes in this PR and they fill all or part of the acceptance criteria of the ticket, and the code is in a mergeable state.
46-
- [ ] If there were infrastructure, operational, or build changes, I have made sure there is sufficient evidence that the changes will work.
47-
- [ ] I have ensured the changelog has been updated by the submitter, if necessary.
78+
## 🚀 Post-merge
4879

49-
## Post-merge
80+
<!-- Actions to complete after merging -->
5081

51-
After merging and deploying changes to the sandbox, Postman collection or spec examples please run the `Run Postman collection` workflow.
82+
After merging and deploying changes to the sandbox, Postman collection or spec examples please run the Run Postman
83+
collection workflow.
5284

5385
This will run the tests within the collection to check that the sandbox is working as expected once deployed.

0 commit comments

Comments
 (0)