Skip to content

Commit b980ffb

Browse files
authored
Create pull_request_template.md (#14)
1 parent c86e074 commit b980ffb

File tree

1 file changed

+55
-0
lines changed

1 file changed

+55
-0
lines changed

.github/pull_request_template.md

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
## Breaking change
2+
<!--
3+
If your PR contains a breaking change for existing users, it is important
4+
to tell them what breaks, how to make it work again and why we did this.
5+
This piece of text is published with the release notes, so it helps if you
6+
write it towards our users, not us.
7+
Note: Remove this section if this PR is NOT a breaking change.
8+
-->
9+
10+
11+
## Proposed change
12+
<!--
13+
Describe the big picture of your changes here to communicate to the
14+
maintainers why we should accept this pull request. If it fixes a bug
15+
or resolves a feature request, be sure to link to that issue in the
16+
additional information section.
17+
-->
18+
19+
20+
## Type of change
21+
<!--
22+
What type of change does your PR introduce to Pledger.io?
23+
NOTE: Please, check only 1! box!
24+
If your PR requires multiple boxes to be checked, you'll most likely need to
25+
split it into multiple PRs. This makes things easier and faster to code review.
26+
-->
27+
28+
- [ ] Dependency upgrade
29+
- [ ] Bugfix (non-breaking change which fixes an issue)
30+
- [ ] New feature (which adds functionality to the application)
31+
- [ ] Deprecation (breaking change to happen in the future)
32+
- [ ] Breaking change (fix/feature causing existing functionality to break)
33+
- [ ] Code quality improvements to existing code or addition of tests
34+
35+
## Additional information
36+
<!--
37+
Details are important, and help maintainers processing your PR.
38+
Please be sure to fill out additional details, if applicable.
39+
-->
40+
41+
- This PR fixes or closes issue: fixes #
42+
- This PR is related to issue:
43+
44+
## Checklist
45+
<!--
46+
Put an `x` in the boxes that apply. You can also fill these out after
47+
creating the PR. If you're unsure about any of them, don't hesitate to ask.
48+
We're here to help! This is simply a reminder of what we are going to look
49+
for before merging your code.
50+
-->
51+
52+
- [ ] The code change is tested and works locally.
53+
- [ ] Local tests pass. **Your PR cannot be merged unless tests pass**
54+
- [ ] There is no commented out code in this PR.
55+
- [ ] Tests have been added to verify that the new code works.

0 commit comments

Comments
 (0)