Skip to content

Commit 0db7e7b

Browse files
committed
chore: update pull request template
1 parent 00c3b95 commit 0db7e7b

File tree

1 file changed

+30
-18
lines changed

1 file changed

+30
-18
lines changed

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 30 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,36 @@
1-
<!--- Provide a general summary of your changes in the title above -->
1+
<!---
2+
☝️ PR title should follow conventional commits (https://conventionalcommits.org)
23
3-
## Types of changes
4-
<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
5-
- [ ] Bug fix (a non-breaking change which fixes an issue)
6-
- [ ] New feature (a non-breaking change which adds functionality)
7-
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
4+
Please carefully read the contribution docs before creating a pull request
5+
👉 https://nuxt.com/docs/community/contribution
6+
-->
87

8+
### 🔗 Linked issue
99

10-
## Description
11-
<!--- Describe your changes in detail -->
12-
<!--- Why is this change required? What problem does it solve? -->
13-
<!--- If it resolves an open issue, please link to the issue here. For example "Resolves: #1337" -->
10+
<!-- Please ensure there is an open issue and mention its number as #123 -->
1411

12+
### ❓ Type of change
1513

16-
## Checklist:
17-
<!--- Put an `x` in all the boxes that apply. -->
18-
<!--- If your change requires a documentation PR, please link it appropriately -->
19-
<!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
20-
- [ ] My change requires a change to the documentation.
21-
- [ ] I have updated the documentation accordingly. (PR: #)
22-
- [ ] I have added tests to cover my changes (if not applicable, please state why)
23-
- [ ] All new and existing tests are passing.
14+
<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply. -->
15+
16+
- [ ] 📖 Documentation (updates to the documentation or readme)
17+
- [ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
18+
- [ ] 👌 Enhancement (improving an existing functionality like performance)
19+
- [ ] ✨ New feature (a non-breaking change that adds functionality)
20+
- [ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to change)
21+
22+
### 📚 Description
23+
24+
<!-- Describe your changes in detail -->
25+
<!-- Why is this change required? What problem does it solve? -->
26+
<!-- If it resolves an open issue, please link to the issue here. For example "Resolves #1337" -->
27+
28+
### 📝 Checklist
29+
30+
<!-- Put an `x` in all the boxes that apply. -->
31+
<!-- If your change requires a documentation PR, please link it appropriately -->
32+
<!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
33+
34+
- [ ] I have linked an issue or discussion.
35+
- [ ] I have updated the documentation accordingly.
2436

0 commit comments

Comments
 (0)