|
| 1 | +<!-- Thanks for contributing! --> |
| 2 | +## Summary |
| 3 | +_What conceptually is this PR introducing? If context is already provided from the JIRA ticket, still place it in the |
| 4 | +Pull Request as you should not make the reviewer do digging for a basic summary._ |
| 5 | + |
| 6 | +## Changes in this PR |
| 7 | +_What changes did you make to the code? What new APIs (public or private) were added, removed, or edited to generate |
| 8 | +the desired outcome explained in the above summary?_ |
| 9 | + |
| 10 | +## Test Plan |
| 11 | +_How did you test the code? If you added unit tests, you can say that. If you didn’t introduce unit tests, explain why. |
| 12 | +All code should be tested in some way – so please list what your validation strategy was._ |
| 13 | + |
| 14 | +### Screenshots (optional) |
| 15 | +_Usually a great supplement to a test plan, especially if this requires local testing._ |
| 16 | + |
| 17 | +## Checklist |
| 18 | +### Checklist for Author |
| 19 | +- [ ] Did you update the changelog (if necessary)? |
| 20 | +- [ ] Is the intention of the code captured in relevant tests? |
| 21 | +- [ ] If there are new TODOs, has a related JIRA ticket been created? |
| 22 | + |
| 23 | +### Checklist for Reviewer {@primary_reviewer} |
| 24 | +- [ ] Does the title of the PR reference a JIRA Ticket? |
| 25 | +- [ ] Do you fully understand the implementation? (Would you be comfortable explaining how this code works to someone else?) |
| 26 | +- [ ] Have you checked for spelling & grammar errors? |
| 27 | +- [ ] Is all relevant documentation (README or docstring) updated? |
| 28 | + |
| 29 | +## Focus Areas for Reviewer |
| 30 | +_List any complex portion of code you believe needs additional scrutiny and explain why._ |
| 31 | + |
| 32 | +<!-- See also: https://docs.google.com/document/d/1Z-z6BDIBJ9G4fn4MBb7Ql5A1NiSY6nsLfEE3KuU_Btw/edit?tab=t.exaie3tsb7gl#heading=h.asd8fqlsyzb6 --> |
0 commit comments