Update PULL_REQUEST_TEMPLATE.md

Signed-off-by: LUIZ HAMILTON ROBERTO DA SILVA <[email protected]>

Author: brazilianscriptguy

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,52 +1,42 @@
-<div>
-  <h1>🚀 Pull Request Template</h1>
-
-  <h2>📝 Description</h2>
-  <p>
-    Please include a <strong>summary of the changes</strong> and the related issue. Explain the <strong>rationale behind the changes</strong>, focusing on the problem that the pull request is solving.
-  </p>
-
-  <h2>🔗 Related Issue</h2>
-  <p>
-    Link to the issue that this pull request addresses (e.g., <code>Fixes #123</code>).
-  </p>
-
-  <h2>🛠️ Type of Change</h2>
-  <p>Please select the type of change by marking the relevant checkboxes:</p>
-  <ul>
-    <li>🐞 <strong>Bug fix</strong> (non-breaking change which fixes an issue)</li>
-    <li>✨ <strong>New feature</strong> (non-breaking change which adds functionality)</li>
-    <li>🔥 <strong>Breaking change</strong> (fix or feature that would cause existing functionality to not work as expected)</li>
-    <li>📚 <strong>Documentation update</strong> (if none of the above apply)</li>
-  </ul>
-
-  <h2>🧪 How Has This Been Tested?</h2>
-  <p>
-    Please describe the <strong>tests that you ran</strong> to verify your changes. Provide instructions so that others can reproduce them:
-  </p>
-  <ul>
-    <li>✅ <strong>Test A:</strong> [Description of Test A]</li>
-    <li>✅ <strong>Test B:</strong> [Description of Test B]</li>
-  </ul>
-  <p>
-    Include details of your <strong>test environment</strong>, including the OS version, PowerShell version, and any other relevant software.
-  </p>
-
-  <h2>☑️ Checklist</h2>
-  <p>Ensure that your pull request meets the following criteria:</p>
-  <ul>
-    <li>🧼 <strong>Code follows the style guidelines</strong> of this project</li>
-    <li>🔍 <strong>Self-review</strong> of my own code</li>
-    <li>💬 <strong>Commented my code</strong>, particularly in hard-to-understand areas</li>
-    <li>📄 <strong>Corresponding changes</strong> have been made to the documentation</li>
-    <li>🚫 <strong>No new warnings</strong> have been introduced</li>
-    <li>✅ <strong>Added tests</strong> that prove my fix is effective or that my feature works</li>
-    <li>🧪 <strong>New and existing unit tests</strong> pass locally with my changes</li>
-    <li>🔗 <strong>Any dependent changes</strong> have been merged and published in downstream modules</li>
-  </ul>
-
-  <h2>🗒️ Additional Notes</h2>
-  <p>
-    Add any <strong>additional information</strong> that might be useful when reviewing your pull request.
-  </p>
-</div>
+# 🚀 Pull Request
+
+## 📝 Description
+Provide a **summary of the changes** and the **rationale** (what problem this PR solves).
+
+## 🔗 Related Issue
+Link the issue this PR addresses (example: `Fixes #123`)
+
+- Fixes #
+
+## 🛠️ Type of Change
+Select the type of change:
+
+- [ ] 🐞 Bug fix (non-breaking change that fixes an issue)
+- [ ] ✨ New feature (non-breaking change that adds functionality)
+- [ ] 🔥 Breaking change (fix or feature that changes existing behavior)
+- [ ] 📚 Documentation update
+
+## 🧪 How Has This Been Tested?
+Describe the tests you ran and how to reproduce them.
+
+**Tests executed:**
+- ✅ Test A:
+- ✅ Test B:
+
+**Test environment:**
+- OS:
+- PowerShell:
+- Other relevant details:
+
+## ☑️ Checklist
+- [ ] 🧼 Code follows the style guidelines of this project
+- [ ] 🔍 Self-reviewed my own code
+- [ ] 💬 Added comments in hard-to-understand areas (when needed)
+- [ ] 📄 Updated documentation (if applicable)
+- [ ] 🚫 No new warnings introduced
+- [ ] ✅ Added tests that prove the fix/feature works (if applicable)
+- [ ] 🧪 New and existing tests pass locally (if applicable)
+- [ ] 🔗 Any dependent changes have been merged/published (if applicable)
+
+## 🗒️ Additional Notes
+Add any extra context for reviewers (screenshots, logs, follow-ups, etc.).