Skip to content

Commit be33c28

Browse files
authored
Update PR template for new etiquette guidelines (#2093)
1 parent 37fa863 commit be33c28

File tree

1 file changed

+23
-4
lines changed

1 file changed

+23
-4
lines changed

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 23 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,24 @@
1-
### All Submissions:
1+
# Summary
2+
3+
<!-- Enter your issue summary here.-->
4+
5+
## Proof of Work
6+
7+
<!-- Enter your proof that it works here.-->
8+
9+
## Checklist
10+
- [ ] Have you linked a jira ticket and/or is the ticket in the title?
11+
- [ ] Have you checked whether your jira ticket required DOCSP changes?
12+
- [ ] Have you checked for release_note changes?
13+
- [ ] Have you signed our [CLA](https://www.mongodb.com/legal/contributor-agreement)?
14+
15+
## Reminder (Please remove this when merging)
16+
- Please try to Approve or Reject Changes the PR, keep PRs in review as short as possible
17+
- Remember the following Communication Standards - use comment prefixes for clarity:
18+
* **blocking**: Must be addressed before approval.
19+
* **follow-up**: Can be addressed in a later PR or ticket.
20+
* **q**: Clarifying question.
21+
* **nit**: Non-blocking suggestions.
22+
* **note**: Side-note, non-actionable. Example: Praise
23+
* --> no prefix is considered a question
224

3-
* [ ] Have you signed our [CLA](https://www.mongodb.com/legal/contributor-agreement)?
4-
* [ ] Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if there is one).
5-
* [ ] Update docs/release-notes/release-notes-template.md if your changes should be included in the release notes for the next release.

0 commit comments

Comments
 (0)