Skip to content

Commit b8c68cf

Browse files
authored
Reformatted PR template
1 parent 4475f29 commit b8c68cf

File tree

1 file changed

+8
-20
lines changed

1 file changed

+8
-20
lines changed

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 8 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,50 +1,38 @@
11
[Issue Key](https://jira.mongodb.org/browse/{ISSUE_KEY})
22

3-
43
## Summary
4+
55
<!-- What is this PR introducing? If context is already provided from the JIRA ticket, still place it in the Pull Request as you should not make the reviewer do digging for a basic summary. -->
6-
## Changes in this PR
76

7+
## Changes in this PR
88

99
<!-- What changes did you make to the code? What new APIs (public or private) were added, removed, or edited to generate the desired outcome explained in the above summary? -->
1010

11-
1211
## Test Plan
1312

14-
1513
<!-- How did you test the code? If you added unit tests, you can say that. If you didn’t introduce unit tests, explain why. All code should be tested in some way – so please list what your validation strategy was. -->
1614

17-
1815
### Screenshots (optional)
1916

20-
2117
<!-- Usually a great supplement to a test plan, especially if this requires local testing. -->
2218

23-
2419
## Checklist
2520

26-
2721
<!-- Do not delete the items provided on this checklist -->
2822

29-
3023
### Checklist for Author
3124

32-
33-
- [ ] Did you update the changelog (if necessary)?
34-
- [ ] Is the intention of the code captured in relevant tests?
25+
- [ ] Did you update the changelog (if necessary)?
26+
- [ ] Is the intention of the code captured in relevant tests?
3527
- [ ] If there are new TODOs, has a related JIRA ticket been created?
3628

29+
### Checklist for Reviewer {@primary_reviewer}
3730

38-
### Checklist for Reviewer {@primary\_reviewer}
39-
40-
41-
- [ ] Does the title of the PR reference a JIRA Ticket?
42-
- [ ] Do you fully understand the implementation? (Would you be comfortable explaining how this code works to someone else?)
43-
- [ ] Have you checked for spelling & grammar errors?
31+
- [ ] Does the title of the PR reference a JIRA Ticket?
32+
- [ ] Do you fully understand the implementation? (Would you be comfortable explaining how this code works to someone else?)
33+
- [ ] Have you checked for spelling & grammar errors?
4434
- [ ] Is all relevant documentation (README or docstring) updated?
4535

46-
4736
## Focus Areas for Reviewer
4837

49-
5038
<!-- List any complex portion of code you believe needs additional scrutiny and explain why. -->

0 commit comments

Comments
 (0)