chore: remove fluff from PR-template (#5941)

.github/ISSUE_TEMPLATE/ask_for_help.yml

@@ -3,7 +3,7 @@ name: ❓ Ask for help
 description: |
   Submit any question related to Uptime Kuma
 #title: "[Help]"
-labels: ["help", "P3-low"]
+labels: ["help"]
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -3,7 +3,7 @@ name: 🐛 Bug Report
 description: |
   Submit a bug report to help us improve
 #title: "[Bug]"
-labels: ["bug", "P2-medium"]
+labels: ["bug"]
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -3,7 +3,7 @@ name: 🚀 Feature Request
 description: |
   Submit a proposal for a new feature
 # title: "[Feature]"
-labels: ["feature-request", "P3-low"]
+labels: ["feature-request"]
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/security_issue.yml

@@ -3,7 +3,7 @@ name: 🛡️ Security Issue
 description: |
   Notify Louis Lam about a security concern. Please do NOT include any sensitive details in this issue.
 # title: "Security Issue"
-labels: ["security", "P1-high"]
+labels: ["security"]
 assignees: [louislam]
 body:
   - type: markdown

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,10 +1,10 @@
-**⚠️ Please Note: We do not accept all types of pull requests, and we want to ensure we don’t waste your time. Before submitting, make sure you have read our pull request guidelines: [Pull Request Rules](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma)**
-
 ## ❗ Important Announcement
 
 <details><summary>Click here for more details:</summary>
 </p>
 
+**⚠️ Please Note: We do not accept all types of pull requests, and we want to ensure we don’t waste your time. Before submitting, make sure you have read our pull request guidelines: [Pull Request Rules](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma)**
+
 ### 🚧 Temporary Delay in Feature Requests and Pull Request Reviews
 
 **At this time, we may be slower to respond to new feature requests and review pull requests. Existing requests and PRs will remain in the backlog but may not be prioritized immediately.**
@@ -26,16 +26,22 @@ We appreciate your patience and understanding as we continue to improve Uptime K
 
 ## 📋 Overview
 
-Provide a clear summary of the purpose and scope of this pull request:
+<!-- Provide a clear summary of the purpose and scope of this pull request:-->
 
 - **What problem does this pull request address?**
-
   - Please provide a detailed explanation here.
-
 - **What features or functionality does this pull request introduce or enhance?**
-
   - Please provide a detailed explanation here.
 
+## 🔗 Related Issues
+
+<!--
+Please link any GitHub issues or tasks that this pull request addresses. Use the appropriate issue numbers or links.
+-->
+
+- Relates to #issue-number
+- Resolves #issue-number
+
 ## 🔄 Changes
 
 ### 🛠️ Type of change
@@ -52,19 +58,7 @@ Provide a clear summary of the purpose and scope of this pull request:
 - [ ] 🔧 Other (please specify):
   - Provide additional details here.
 
-## 🔗 Related Issues
-
-<!--
-Please link any GitHub issues or tasks that this pull request addresses. Use the appropriate issue numbers or links.
-
-**Note**: Include only issues directly related to this PR. Remove any irrelevant reference.
--->
-
-- Relates to #issue-number
-- Resolves #issue-number
-- Fixes #issue-number
-
-## 📄 Checklist *
+## 📄 Checklist
 
 <!-- Please select all options that apply -->
 
@@ -97,26 +91,3 @@ If not, remove this section.
 | `DOWN`             | ![Before](image-link) | ![After](image-link) |
 | Certificate-expiry | ![Before](image-link) | ![After](image-link) |
 | Testing            | ![Before](image-link) | ![After](image-link) |
-
-## ℹ️ Additional Context
-
-Provide any relevant details to assist reviewers in understanding the changes.
-
-<details><summary>Click here for more details:</summary>
-</p>
-
-**Key Considerations**:
-
-- **Design decisions** – Key choices or trade-offs made during development.
-- **Alternative solutions** – Approaches considered but not implemented, along with reasons.
-- **Relevant links** – Specifications, discussions, or resources that provide context.
-- **Dependencies** – Related pull requests or issues that must be resolved before merging.
-- **Additional context** – Any other details that may help reviewers understand the changes.
-
-Provide details here
-
-## 💬 Requested Feedback
-
-<!-- If a part of our docs is unclear, you are unsure how to do something/.. this is where we would appreciate your feedback -->
-
-- `Mention documents needing feedback here`