Skip to content

Commit c71b9dc

Browse files
authored
chore: add pull request template (#550)
Adds pull request template. Signed-off-by: Ryan Johnson <[email protected]>
1 parent 7c3689a commit c71b9dc

File tree

1 file changed

+80
-0
lines changed

1 file changed

+80
-0
lines changed

.github/pull_request_template.md

Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
<!-- markdownlint-disable first-line-h1 no-inline-html -->
2+
3+
<!--
4+
NOTE: Do not enter content between the comment markers <!- and ->.
5+
6+
In order to have the best experience with our community, we recommend that you read the code of conduct and contributing guidelines before submitting a pull request.
7+
8+
By submitting this pull request, you confirm that you have read, understood, and agreed to the project's code of conduct and contributing guidelines.
9+
10+
Please use conventional commits to format the title of the pull request and the commit messages.
11+
For more information, please refer to https://www.conventionalcommits.org.
12+
-->
13+
14+
### Summary
15+
16+
<!--
17+
Please provide a clear and concise description of the pull request.
18+
-->
19+
20+
### Type
21+
22+
<!--
23+
Please check the one(s) that applies to this pull request using "x".
24+
-->
25+
26+
- [ ] This is a bug fix.
27+
- [ ] This is an enhancement or feature.
28+
- [ ] This is a code style/formatting update.
29+
- [ ] This is a documentation update.
30+
- [ ] This is a refactoring update.
31+
- [ ] This is a chore update
32+
- [ ] This is something else.
33+
Please describe:
34+
35+
### Breaking Changes?
36+
37+
<!--
38+
Please check the one that applies to this pull request using "x".
39+
If this pull request contains a breaking change, please describe the impact and mitigation path.
40+
-->
41+
42+
- [ ] Yes, there are breaking changes.
43+
- [ ] No, there are no breaking changes.
44+
45+
### Test and Documentation
46+
47+
<!--
48+
Please check the one(s) that applies to this pull request using "x".
49+
For bug fixes and enhancements/features, please ensure that tests and documentation have been completed and provide details.
50+
-->
51+
52+
- [ ] Tests have been completed.
53+
- [ ] Documentation has been added or updated.
54+
55+
<!--
56+
Please describe the tests that have been completed and/or the documentation that has been added/updated.
57+
-->
58+
59+
### Issue References
60+
61+
<!--
62+
Is this related to any GitHub issue(s)? If so, please provide the issue number(s) that are closed or resolved by this pull request.
63+
64+
For bug fixes and enhancements/features, please ensure that a GitHub issue has been created and provide the issue number(s) here.
65+
66+
Please use the 'Closes', 'Resolves', or 'Fixes' keywords followed by the a hash and issue number.
67+
This will link the pull request to the issue(s) and automatically close them when the pull request is merged.
68+
69+
Example:
70+
71+
Closes #000
72+
Resolves #001
73+
Fixes #002
74+
-->
75+
76+
### Additional Information
77+
78+
<!--
79+
Please provide any additional information that may be helpful.
80+
-->

0 commit comments

Comments
 (0)