Skip to content

Commit 0b68d22

Browse files
Merge pull request #7 from thriving-dev/feat/gh-pr-template
feat: adds GitHub PR template
2 parents 4300e5f + 0c97a28 commit 0b68d22

File tree

1 file changed

+34
-0
lines changed

1 file changed

+34
-0
lines changed

.github/PULL_REQUEST_TEMPLATE

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
<!-- ☝️ PR title should follow conventional commits (https://conventionalcommits.org) -->
2+
<!-- Thanks for taking the time to write this Pull Request! ❤️ -->
3+
4+
### ❓ Type of change
5+
6+
<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply. -->
7+
8+
- [ ] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
9+
- [ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
10+
- [ ] 👌 Enhancement (improving an existing functionality like performance)
11+
- [ ] ✨ New feature (a non-breaking change that adds functionality)
12+
- [ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
13+
- [ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to change)
14+
15+
### 📚 Description, Motivation and Context
16+
17+
<!-- Describe your changes in detail -->
18+
<!-- Why is this change required? What problem does it solve? -->
19+
<!-- If it resolves an open issue, please link to the issue here. For example "Resolves #1337" -->
20+
21+
### 🧪 How Has This Been Tested?
22+
23+
<!-- Please describe in detail how you tested your changes. -->
24+
<!-- Include details of your testing environment, tests ran to see how -->
25+
<!-- your change affects other areas of the code, etc. -->
26+
27+
### 📝 Checklist
28+
29+
<!-- Put an `x` in all the boxes that apply. -->
30+
<!-- If your change requires a documentation PR, please link it appropriately -->
31+
<!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
32+
33+
- [ ] I have linked an issue or discussion.
34+
- [ ] I have updated the documentation accordingly.

0 commit comments

Comments
 (0)