From 2d69fbecfdbcb1a50ceb707771cc689ab2ad78b0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Damian=20G=C5=82owala?= <damian.glowala.rebkow@gmail.com>
Date: Sat, 20 Apr 2024 11:47:44 +0200
Subject: [PATCH] chore: improve PR template (#65)

---
 .github/PULL_REQUEST_TEMPLATE.md | 36 ++++++++++----------------------
 1 file changed, 11 insertions(+), 25 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index d3ae061..39757f4 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,33 +1,19 @@
-<!---
-☝️ PR title should follow conventional commits (https://conventionalcommits.org)
--->
-
 ### 🔗 Linked issue
 
-<!-- Please ensure there is an open issue and mention its number as #123 -->
-
-### ❓ Type of change
-
-<!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply. -->
-
-- [ ] 📖 Documentation (updates to the documentation, readme or JSDoc annotations)
-- [ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
-- [ ] 👌 Enhancement (improving an existing functionality like performance)
-- [ ] ✨ New feature (a non-breaking change that adds functionality)
-- [ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
-- [ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to change)
+<!-- Please ensure there is an open issue and mention its number. For example, "resolves #123" -->
 
 ### 📚 Description
 
-<!-- Describe your changes in detail -->
-<!-- Why is this change required? What problem does it solve? -->
-<!-- If it resolves an open issue, please link to the issue here. For example "Resolves #1337" -->
+<!-- Describe your changes in detail. Why is this change required? What problem does it solve? -->
 
-### 📝 Checklist
+<!----------------------------------------------------------------------
+Before creating the pull request, please make sure you do the following:
 
-<!-- Put an `x` in all the boxes that apply. -->
-<!-- If your change requires a documentation PR, please link it appropriately -->
-<!-- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
+- Check that there isn't already a PR that solves the problem the same way. If you find a duplicate, please help us reviewing it.
+- Read the contribution docs at https://nuxt.com/docs/community/contribution
+- Ensure that PR title follows conventional commits (https://www.conventionalcommits.org)
+- Update the corresponding documentation if needed.
+- Include relevant tests that fail without this PR but pass with it.
 
-- [ ] I have linked an issue or discussion.
-- [ ] I have updated the documentation accordingly.
+Thank you for contributing to Nuxt Google Tag!
+----------------------------------------------------------------------->