Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
34 lines
1.6 KiB
Markdown
34 lines
1.6 KiB
Markdown
<!-- Thanks for contributing! -->
|
||
<!-- Please ensure that the title of the PR is in the following form:
|
||
[JIRA TICKET]: Issue Title
|
||
|
||
If you are an external contributor and there is no JIRA ticket associated with your change, then use your best judgement
|
||
for the PR title. A MongoDB employee will create a JIRA ticket and edit the name and links as appropriate.
|
||
|
||
Note on AI Contributions:
|
||
We only accept pull requests that are authored and submitted by human contributors who fully understand the changes they are proposing.
|
||
All contributions must be written and understood by human contributors. Please read about our policy in our contributing guide.
|
||
-->
|
||
[JIRA TICKET]
|
||
|
||
## Changes in this PR
|
||
<!-- 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? -->
|
||
|
||
## Test Plan
|
||
<!-- 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. -->
|
||
|
||
## Checklist
|
||
<!-- Do not delete the items provided on this checklist. -->
|
||
|
||
### Checklist for Author
|
||
- [ ] Did you update the changelog (if necessary)?
|
||
- [ ] Is there test coverage?
|
||
- [ ] Is any followup work tracked in a JIRA ticket? If so, add link(s).
|
||
|
||
### Checklist for Reviewer
|
||
- [ ] Does the title of the PR reference a JIRA Ticket?
|
||
- [ ] Do you fully understand the implementation? (Would you be comfortable explaining how this code works to someone else?)
|
||
- [ ] Is all relevant documentation (README or docstring) updated?
|