11<!-- Thanks for contributing! -->
22## 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._
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. -->
55
66## 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?_
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? -->
99
1010## 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._
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. -->
1313
1414### Screenshots (optional)
15- _ Usually a great supplement to a test plan, especially if this requires local testing._
15+ <!-- Usually a great supplement to a test plan, especially if this requires local testing. -->
1616
1717## Checklist
18+ <!-- Do not delete the items provided on this checklist. -->
1819### Checklist for Author
1920- [ ] Did you update the changelog (if necessary)?
2021- [ ] Is the intention of the code captured in relevant tests?
@@ -27,6 +28,6 @@ _Usually a great supplement to a test plan, especially if this requires local te
2728- [ ] Is all relevant documentation (README or docstring) updated?
2829
2930## Focus Areas for Reviewer
30- _ List any complex portion of code you believe needs additional scrutiny and explain why._
31+ <!-- List any complex portion of code you believe needs additional scrutiny and explain why. -->
3132
3233<!-- See also: https://docs.google.com/document/d/1Z-z6BDIBJ9G4fn4MBb7Ql5A1NiSY6nsLfEE3KuU_Btw/edit?tab=t.exaie3tsb7gl#heading=h.asd8fqlsyzb6 -->
0 commit comments