Skip to content

Commit 0c28a5a

Browse files
projectgusdpgeorge
authored andcommitted
github: Add Pull Request template.
Provides pull request submitters with contributor documentation, and prompts them to provide relevant information about testing, and how they came to implement this change. Sections are deliberately small so they don't crowd out the GitHub Pull Request description text field. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <[email protected]>
1 parent 206dc09 commit 0c28a5a

File tree

1 file changed

+33
-0
lines changed

1 file changed

+33
-0
lines changed

.github/pull_request_template.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
<!-- Thanks for submitting a Pull Request! We appreciate you spending the
2+
time to improve MicroPython. Please provide enough information so that
3+
others can review your Pull Request.
4+
5+
Before submitting, please read:
6+
https://github.com/micropython/micropython/blob/master/CODEOFCONDUCT.md
7+
https://github.com/micropython/micropython/wiki/ContributorGuidelines
8+
9+
Please check any CI failures that appear after your Pull Request is opened.
10+
-->
11+
12+
### Summary
13+
14+
<!-- Explain the reason for making this change. What problem does the pull request
15+
solve, or what improvement does it add? Add links if relevant. -->
16+
17+
18+
### Testing
19+
20+
<!-- Explain what testing you did, and on which boards/ports. If there are
21+
boards or ports that you couldn't test, please mention this here as well.
22+
23+
If you leave this empty then your Pull Request may be closed. -->
24+
25+
26+
### Trade-offs and Alternatives
27+
28+
<!-- If the Pull Request has some negative impact (i.e. increased code size)
29+
then please explain why you think the trade-off improvement is worth it.
30+
If you can think of alternative ways to do this, please explain that here too.
31+
32+
Delete this heading if not relevant (i.e. small fixes) -->
33+

0 commit comments

Comments
 (0)