Skip to content

Commit e3d9357

Browse files
authored
Create pull_request_template.md
1 parent 3ab4bcd commit e3d9357

File tree

1 file changed

+39
-0
lines changed

1 file changed

+39
-0
lines changed
Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
## Proposed changes
2+
3+
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
4+
5+
## Types of changes
6+
7+
_Put an `x` in the boxes that apply._
8+
9+
- [ ] Bugfix (non-breaking change which fixes an issue)
10+
- [ ] New feature (non-breaking change which adds functionality)
11+
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
12+
- [ ] Refactoring (no functional changes, no api changes)
13+
- [ ] Code style update (formatting, renaming)
14+
- [ ] Build related changes (workflow changes)
15+
- [ ] Documentation Update (readme, changelog)
16+
- [ ] Other, please describe:
17+
18+
19+
## Issue
20+
Include a link to the issue if applicable, otherwise you can remove this section.
21+
22+
## What is the current behavior?
23+
Please describe the current behavior that you are modifying.
24+
25+
## What is the new behavior?
26+
Please describe the behavior or changes that are being added by this PR.
27+
28+
## Checklist
29+
30+
_Put an `x` in the boxes that apply._
31+
32+
- [ ] The code compiles
33+
- [ ] I have tested that this doesn't break existing code (unless it is an explicit breaking change)
34+
- [ ] I have tested that the (new) functionality/fix works as intended
35+
- [ ] I have added necessary documentation (if appropriate)
36+
37+
## Further comments
38+
39+
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

0 commit comments

Comments
 (0)