From 1968ae620cbe3118ca8a984e34d05dcc86a1cfdf Mon Sep 17 00:00:00 2001
From: GJS <homelab.api@gmail.com>
Date: Tue, 25 Mar 2025 12:50:22 +0100
Subject: [PATCH 01/11] Updated: Enhance ask-for-help template with new
 guidelines and structure

- Added a new section to discourage unnecessary pings to maintainers, ensuring better focus on high-priority tasks.
- Introduced a checkbox to acknowledge understanding of the new pinging guidelines.
- Streamlined issue submission process by emphasizing the importance of checking for duplicate issues before submitting.
- Enhanced security policy section to ensure users agree to review it before reporting security-related issues.
- Reorganized the template for clearer communication and improved user engagement.

modified: .github/ISSUE_TEMPLATE/ask-for-help.yaml
---
 .github/ISSUE_TEMPLATE/ask-for-help.yaml | 58 +++++++++++++++++++-----
 1 file changed, 46 insertions(+), 12 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/ask-for-help.yaml b/.github/ISSUE_TEMPLATE/ask-for-help.yaml
index a708dbf23..082308ba5 100644
--- a/.github/ISSUE_TEMPLATE/ask-for-help.yaml
+++ b/.github/ISSUE_TEMPLATE/ask-for-help.yaml
@@ -1,22 +1,48 @@
 name: "❓ Ask for help"
 description: "Submit any question related to Uptime Kuma"
 #title: "[Help] "
-labels: [help]
+labels: ["help", "P3: low"]
 body:
+  - type: "markdown"
+    attributes:
+      value: |
+        ## **❗ Important: Please Avoid Unnecessary Pinging of Maintainers**
+
+        **We kindly ask users to refrain from pinging maintainers unless absolutely necessary. Pings should be reserved for critical issues or urgent matters that require immediate attention.**
+
+        - **Why**: To help maintainers focus on high-priority tasks, we kindly request that unnecessary or repeated pings be minimized. This will help ensure quicker responses for matters that truly need attention.
+        - **What This Means**: Non-urgent pings may be ignored or addressed later. Please assess the urgency of your request before pinging a maintainer.
+  - type: checkboxes
+    id: unnecessary-pinging-of-maintainers
+    attributes:
+      label:
+        "I have read and understand that unnecessary pings to maintainers will
+        not be tolerated."
+      options:
+        - label:
+            "I understand that my ping will be ignored if deemed unnecessary or
+            repetitive."
+          required: true
   - type: checkboxes
     id: no-duplicate-issues
     attributes:
       label: "⚠️ Please verify that this question has NOT been raised before."
-      description: "Search in the issues sections by clicking [HERE](https://github.com/louislam/uptime-kuma/issues?q=)"
+      description:
+        "Search in the issues sections by clicking
+        [HERE](https://github.com/louislam/uptime-kuma/issues?q=)"
       options:
         - label: "I checked and didn't find similar issue"
           required: true
   - type: checkboxes
     attributes:
       label: "🛡️ Security Policy"
-      description: Please review the security policy before reporting security related issues/bugs.
+      description:
+        Please review the security policy before reporting security related
+        issues/bugs.
       options:
-        - label: I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy)
+        - label:
+            I agree to have read this project [Security
+            Policy](https://github.com/louislam/uptime-kuma/security/policy)
           required: true
   - type: textarea
     id: steps-to-reproduce
@@ -24,7 +50,9 @@ body:
       required: true
     attributes:
       label: "📝 Describe your problem"
-      description: "Please walk us through it step by step. Include all important details and add screenshots where appropriate"
+      description:
+        "Please walk us through it step by step. Include all important details
+        and add screenshots where appropriate"
       placeholder: "Describe what are you asking for..."
   - type: textarea
     id: error-msg
@@ -36,7 +64,9 @@ body:
     id: uptime-kuma-version
     attributes:
       label: "🐻 Uptime-Kuma Version"
-      description: "Which version of Uptime-Kuma are you running? Please do NOT provide the docker tag such as latest or 1"
+      description:
+        "Which version of Uptime-Kuma are you running? Please do NOT provide the
+        docker tag such as latest or 1"
       placeholder: "Ex. 1.10.0"
     validations:
       required: true
@@ -44,7 +74,9 @@ body:
     id: operating-system
     attributes:
       label: "💻 Operating System and Arch"
-      description: "Which OS is your server/device running on? (For Replit, please do not report this bug)"
+      description:
+        "Which OS is your server/device running on? (For Replit, please do not
+        report this bug)"
       placeholder: "Ex. Ubuntu 20.04 x86"
     validations:
       required: true
@@ -52,7 +84,9 @@ body:
     id: browser-vendor
     attributes:
       label: "🌐 Browser"
-      description: "Which browser are you running on? (For Replit, please do not report this bug)"
+      description:
+        "Which browser are you running on? (For Replit, please do not report
+        this bug)"
       placeholder: "Ex. Google Chrome 95.0.4638.69"
     validations:
       required: true
@@ -67,9 +101,9 @@ body:
           - **Filesystem used to store the database on**: Windows/ZFS/btrfs/NFSv3 on a SSD/HDD/eMMC
           - **number of monitors**: 42
       value: |
-        - Runtime: 
-        - Database: 
-        - Filesystem used to store the database on: 
-        - number of monitors: 
+        - Runtime:
+        - Database:
+        - Filesystem used to store the database on:
+        - number of monitors:
     validations:
       required: true

From 08724ed82aca6db44fccb936a6596cbbb7ea5bd9 Mon Sep 17 00:00:00 2001
From: GJS <homelab.api@gmail.com>
Date: Tue, 25 Mar 2025 12:50:50 +0100
Subject: [PATCH 02/11] Updated: Enhance bug report template with new
 guidelines and structure

- Added a markdown section to discourage unnecessary pings to maintainers, ensuring focused responses to urgent issues.
- Introduced a checkbox to confirm understanding of the new pinging policy.
- Updated the labels and assignees to improve issue categorization and accountability.
- Streamlined the bug report process by making related issues search and explanation more prominent.
- Enhanced the security policy section to ensure users acknowledge reading it before submitting security-related bugs.
- Made minor adjustments to field descriptions for clarity and ease of use.

modified: .github/ISSUE_TEMPLATE/bug_report.yaml
---
 .github/ISSUE_TEMPLATE/bug_report.yaml | 65 ++++++++++++++++++++------
 1 file changed, 52 insertions(+), 13 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/bug_report.yaml b/.github/ISSUE_TEMPLATE/bug_report.yaml
index 9745a76a6..28b4b0722 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.yaml
+++ b/.github/ISSUE_TEMPLATE/bug_report.yaml
@@ -1,22 +1,53 @@
 name: "🐛 Bug Report"
 description: "Submit a bug report to help us improve"
 #title: "[Bug] "
-labels: [bug]
+labels: ["bug", "P2: moderate"]
+assignees: ["louislam", "CommanderStorm"]
 body:
+  - type: "markdown"
+    attributes:
+      value: |
+        ## **❗ Important: Please Avoid Unnecessary Pinging of Maintainers**
+
+        **We kindly ask users to refrain from pinging maintainers unless absolutely necessary. Pings should be reserved for critical issues or urgent matters that require immediate attention.**
+
+        - **Why**: To help maintainers focus on high-priority tasks, we kindly request that unnecessary or repeated pings be minimized. This will help ensure quicker responses for matters that truly need attention.
+        - **What This Means**: Non-urgent pings may be ignored or addressed later. Please assess the urgency of your request before pinging a maintainer.
+  - type: checkboxes
+    id: unnecessary-pinging-of-maintainers
+    attributes:
+      label:
+        "I have read and understand that unnecessary pings to maintainers will
+        not be tolerated."
+      options:
+        - label:
+            "I understand that my ping will be ignored if deemed unnecessary or
+            repetitive."
+          required: true
   - type: textarea
     id: related-issues
     validations:
       required: true
     attributes:
       label: "📑 I have found these related issues/pull requests"
-      description: "Search related issues by clicking [HERE](https://github.com/louislam/uptime-kuma/issues?q=) and explain what the difference between them or explain that you are unable to find any related issues"
-      placeholder: "Related to #1 by also touching the ... system. They should not be merged because ..."
+      description:
+        "Search related issues by clicking
+        [HERE](https://github.com/louislam/uptime-kuma/issues?q=) and explain
+        what the difference between them or explain that you are unable to find
+        any related issues"
+      placeholder:
+        "Related to #1 by also touching the ... system. They should not be
+        merged because ..."
   - type: checkboxes
     attributes:
       label: "🛡️ Security Policy"
-      description: Please review the security policy before reporting security related issues/bugs.
+      description:
+        Please review the security policy before reporting security related
+        issues/bugs.
       options:
-        - label: I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy)
+        - label:
+            I agree to have read this project [Security
+            Policy](https://github.com/louislam/uptime-kuma/security/policy)
           required: true
   - type: textarea
     id: description
@@ -31,7 +62,9 @@ body:
       required: true
     attributes:
       label: "👟 Reproduction steps"
-      description: "How do you trigger this bug? Please walk us through it step by step. Include all important details and add screenshots where appropriate"
+      description:
+        "How do you trigger this bug? Please walk us through it step by step.
+        Include all important details and add screenshots where appropriate"
       placeholder: "..."
   - type: textarea
     id: expected-behavior
@@ -53,7 +86,9 @@ body:
     id: uptime-kuma-version
     attributes:
       label: "🐻 Uptime-Kuma Version"
-      description: "Which version of Uptime-Kuma are you running? Please do NOT provide the docker tag such as latest or 1"
+      description:
+        "Which version of Uptime-Kuma are you running? Please do NOT provide the
+        docker tag such as latest or 1"
       placeholder: "Ex. 1.10.0"
     validations:
       required: true
@@ -61,7 +96,9 @@ body:
     id: operating-system
     attributes:
       label: "💻 Operating System and Arch"
-      description: "Which OS is your server/device running on? (For Replit, please do not report this bug)"
+      description:
+        "Which OS is your server/device running on? (For Replit, please do not
+        report this bug)"
       placeholder: "Ex. Ubuntu 20.04 x64 "
     validations:
       required: true
@@ -84,17 +121,19 @@ body:
           - **Filesystem used to store the database on**: Windows/ZFS/btrfs/NFSv3 on a SSD/HDD/eMMC
           - **number of monitors**: 42
       value: |
-        - Runtime: 
-        - Database: 
-        - Filesystem used to store the database on: 
-        - number of monitors: 
+        - Runtime:
+        - Database:
+        - Filesystem used to store the database on:
+        - number of monitors:
     validations:
       required: true
   - type: textarea
     id: logs
     attributes:
       label: "📝 Relevant log output"
-      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      description:
+        Please copy and paste any relevant log output. This will be
+        automatically formatted into code, so no need for backticks.
       render: shell
     validations:
       required: false

From da777030e5b2f518c182ae07bbc802ef17eddabf Mon Sep 17 00:00:00 2001
From: GJS <homelab.api@gmail.com>
Date: Tue, 25 Mar 2025 12:51:40 +0100
Subject: [PATCH 03/11] Update: Implement feature request suspension and new
 guidelines

- Temporarily suspended the acceptance of new feature requests to focus on bug fixes, performance improvements, and critical updates.
- Added a markdown section notifying users about the temporary suspension and the backlog status of existing requests.
- Introduced a checkbox to confirm user understanding of the feature request suspension.
- Enhanced the feature request template with a section about the policy on unnecessary pings to maintainers, including an acknowledgment checkbox.
- Updated labels to include "P4: negligible" and "backlog" for better issue categorization.

modified: .github/ISSUE_TEMPLATE/feature_request.yaml
---
 .github/ISSUE_TEMPLATE/feature_request.yaml | 61 ++++++++++++++++++---
 1 file changed, 54 insertions(+), 7 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/feature_request.yaml b/.github/ISSUE_TEMPLATE/feature_request.yaml
index 531a2c25e..acc0dd585 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.yaml
+++ b/.github/ISSUE_TEMPLATE/feature_request.yaml
@@ -1,16 +1,59 @@
 name: 🚀 Feature Request
 description: "Submit a proposal for a new feature"
-#title: "[Feature] "
-labels: [feature-request]
+# title: "[Feature] "
+labels: ["feature-request", "P4: negligible", "backlog"]
 body:
+  - type: "markdown"
+    attributes:
+      value: |
+        ## **❗ Important: Temporary Suspension of New Feature Requests**
+
+        **At this time, we are not accepting any new feature requests. Existing feature requests will be moved to the backlog and tagged accordingly.**
+
+        - **Reason**: Our current priority is focused on fixing bugs, improving system performance, and implementing essential updates. This temporary suspension will allow us to stabilize the project and ensure smoother management.
+        - **What This Means**: During this period, no new feature requests will be reviewed or accepted. However, we continue to welcome feedback, and all suggestions will be reviewed once the suspension is lifted.
+
+        ## **❗ Important: Please Avoid Unnecessary Pinging of Maintainers**
+
+        **We kindly ask users to refrain from pinging maintainers unless absolutely necessary. Pings should be reserved for critical issues or urgent matters that require immediate attention.**
+
+        - **Why**: To help maintainers focus on high-priority tasks, we kindly request that unnecessary or repeated pings be minimized. This will help ensure quicker responses for matters that truly need attention.
+        - **What This Means**: Non-urgent pings may be ignored or addressed later. Please assess the urgency of your request before pinging a maintainer.
+  - type: checkboxes
+    id: temporary-suspension-of-new-feature-requests
+    attributes:
+      label:
+        "I have read and understand that no new feature requests will be
+        accepted until further notice."
+      options:
+        - label:
+            "I understand that my feature request will be placed in the backlog."
+          required: true
+  - type: checkboxes
+    id: unnecessary-pinging-of-maintainers
+    attributes:
+      label:
+        "I have read and understand that unnecessary pings to maintainers will
+        not be tolerated."
+      options:
+        - label:
+            "I understand that my ping will be ignored if deemed unnecessary or
+            repetitive."
+          required: true
   - type: textarea
     id: related-issues
     validations:
       required: true
     attributes:
       label: "📑 I have found these related issues/pull requests"
-      description: "Search related issues by clicking [HERE](https://github.com/louislam/uptime-kuma/issues?q=) and explain what the difference between them or explain that you are unable to find any related issues"
-      placeholder: "Related to #1 by also touching the ... system. They should not be merged because ..."
+      description:
+        "Search related issues by clicking
+        [HERE](https://github.com/louislam/uptime-kuma/issues?q=) and explain
+        what the difference between them or explain that you are unable to find
+        any related issues"
+      placeholder:
+        "Related to #1 by also touching the ... system. They should not be
+        merged because ..."
   - type: dropdown
     id: feature-area
     attributes:
@@ -38,7 +81,8 @@ body:
       required: true
     attributes:
       label: "🔖 Feature description"
-      description: "A clear and concise description of what the feature request is."
+      description:
+        "A clear and concise description of what the feature request is."
       placeholder: "You should add ..."
   - type: textarea
     id: solution
@@ -54,7 +98,9 @@ body:
       required: false
     attributes:
       label: "❓ Alternatives"
-      description: "A clear and concise description of any alternative solutions or features you've considered."
+      description:
+        "A clear and concise description of any alternative solutions or
+        features you've considered."
       placeholder: "I have considered ..."
   - type: textarea
     id: additional-context
@@ -62,5 +108,6 @@ body:
       required: false
     attributes:
       label: "📝 Additional Context"
-      description: "Add any other context or screenshots about the feature request here."
+      description:
+        "Add any other context or screenshots about the feature request here."
       placeholder: "..."

From 74c784db32506acafa0c6daed7b5bd0a4a1c3d67 Mon Sep 17 00:00:00 2001
From: GJS <homelab.api@gmail.com>
Date: Tue, 25 Mar 2025 12:52:01 +0100
Subject: [PATCH 04/11] Update: Add priority label and clarify security issue
 reporting guidelines

- Added "P1: high" label to security issues for better prioritization.
- Updated markdown instructions to emphasize the importance of using GitHub Security Advisory for reporting vulnerabilities.
- Clarified that this issue is solely for sharing the advisory URL and not for discussing the vulnerability details.
- Retained the step-by-step guide for submitting and sharing the GitHub Security Advisory URL.

modified: .github/ISSUE_TEMPLATE/security_issue.yml
---
 .github/ISSUE_TEMPLATE/security_issue.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/ISSUE_TEMPLATE/security_issue.yml b/.github/ISSUE_TEMPLATE/security_issue.yml
index 0104f9c3c..d6bf7d1e3 100644
--- a/.github/ISSUE_TEMPLATE/security_issue.yml
+++ b/.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]
+labels: ["security", "P1: high"]
 assignees: [louislam]
 body:
   - type: "markdown"

From ed25326ddf9dd4d342c75eee85e490ae375e44e3 Mon Sep 17 00:00:00 2001
From: GJS <homelab.api@gmail.com>
Date: Tue, 25 Mar 2025 16:30:33 +0100
Subject: [PATCH 05/11] Updated: Adjust issue templates for improved clarity
 and usability

- Removed unnecessary checkboxes from issue templates.
- Adjusted labels for better organization and easier searching in the GitHub UI.
- Removed assignees to avoid unnecessary notifications.

modified: .github/ISSUE_TEMPLATE/ask-for-help.yaml
modified: .github/ISSUE_TEMPLATE/bug_report.yaml
modified: .github/ISSUE_TEMPLATE/feature_request.yaml
modified: .github/ISSUE_TEMPLATE/security_issue.yml
---
 .github/ISSUE_TEMPLATE/ask-for-help.yaml    | 14 ++------------
 .github/ISSUE_TEMPLATE/bug_report.yaml      | 15 ++-------------
 .github/ISSUE_TEMPLATE/feature_request.yaml | 14 ++------------
 .github/ISSUE_TEMPLATE/security_issue.yml   |  2 +-
 4 files changed, 7 insertions(+), 38 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/ask-for-help.yaml b/.github/ISSUE_TEMPLATE/ask-for-help.yaml
index 082308ba5..d77e673c6 100644
--- a/.github/ISSUE_TEMPLATE/ask-for-help.yaml
+++ b/.github/ISSUE_TEMPLATE/ask-for-help.yaml
@@ -1,7 +1,8 @@
+---
 name: "❓ Ask for help"
 description: "Submit any question related to Uptime Kuma"
 #title: "[Help] "
-labels: ["help", "P3: low"]
+labels: ["help", "P3-low"]
 body:
   - type: "markdown"
     attributes:
@@ -12,17 +13,6 @@ body:
 
         - **Why**: To help maintainers focus on high-priority tasks, we kindly request that unnecessary or repeated pings be minimized. This will help ensure quicker responses for matters that truly need attention.
         - **What This Means**: Non-urgent pings may be ignored or addressed later. Please assess the urgency of your request before pinging a maintainer.
-  - type: checkboxes
-    id: unnecessary-pinging-of-maintainers
-    attributes:
-      label:
-        "I have read and understand that unnecessary pings to maintainers will
-        not be tolerated."
-      options:
-        - label:
-            "I understand that my ping will be ignored if deemed unnecessary or
-            repetitive."
-          required: true
   - type: checkboxes
     id: no-duplicate-issues
     attributes:
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yaml b/.github/ISSUE_TEMPLATE/bug_report.yaml
index 28b4b0722..6aa8581c5 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.yaml
+++ b/.github/ISSUE_TEMPLATE/bug_report.yaml
@@ -1,8 +1,8 @@
+---
 name: "🐛 Bug Report"
 description: "Submit a bug report to help us improve"
 #title: "[Bug] "
-labels: ["bug", "P2: moderate"]
-assignees: ["louislam", "CommanderStorm"]
+labels: ["bug", "P2-moderate"]
 body:
   - type: "markdown"
     attributes:
@@ -13,17 +13,6 @@ body:
 
         - **Why**: To help maintainers focus on high-priority tasks, we kindly request that unnecessary or repeated pings be minimized. This will help ensure quicker responses for matters that truly need attention.
         - **What This Means**: Non-urgent pings may be ignored or addressed later. Please assess the urgency of your request before pinging a maintainer.
-  - type: checkboxes
-    id: unnecessary-pinging-of-maintainers
-    attributes:
-      label:
-        "I have read and understand that unnecessary pings to maintainers will
-        not be tolerated."
-      options:
-        - label:
-            "I understand that my ping will be ignored if deemed unnecessary or
-            repetitive."
-          required: true
   - type: textarea
     id: related-issues
     validations:
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yaml b/.github/ISSUE_TEMPLATE/feature_request.yaml
index acc0dd585..8e3bb020a 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.yaml
+++ b/.github/ISSUE_TEMPLATE/feature_request.yaml
@@ -1,7 +1,8 @@
+---
 name: 🚀 Feature Request
 description: "Submit a proposal for a new feature"
 # title: "[Feature] "
-labels: ["feature-request", "P4: negligible", "backlog"]
+labels: ["feature-request", "P4-negligible", "backlog"]
 body:
   - type: "markdown"
     attributes:
@@ -29,17 +30,6 @@ body:
         - label:
             "I understand that my feature request will be placed in the backlog."
           required: true
-  - type: checkboxes
-    id: unnecessary-pinging-of-maintainers
-    attributes:
-      label:
-        "I have read and understand that unnecessary pings to maintainers will
-        not be tolerated."
-      options:
-        - label:
-            "I understand that my ping will be ignored if deemed unnecessary or
-            repetitive."
-          required: true
   - type: textarea
     id: related-issues
     validations:
diff --git a/.github/ISSUE_TEMPLATE/security_issue.yml b/.github/ISSUE_TEMPLATE/security_issue.yml
index d6bf7d1e3..ddc5a835f 100644
--- a/.github/ISSUE_TEMPLATE/security_issue.yml
+++ b/.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", "P1-high"]
 assignees: [louislam]
 body:
   - type: "markdown"

From 2368e4386381107b58506ccc31df2f8ec86af631 Mon Sep 17 00:00:00 2001
From: GJS <homelab.api@gmail.com>
Date: Wed, 26 Mar 2025 07:18:10 +0100
Subject: [PATCH 06/11] Updated: Modify pull request template to include delay
 notice

- Added a section informing contributors about potential delays in feature requests and pull request reviews.
- Updated the template to clarify that feature requests and PR reviews may be delayed due to focus on bug fixes and performance improvements.

modified: .github/PULL_REQUEST_TEMPLATE.md
---
 .github/PULL_REQUEST_TEMPLATE.md | 15 ++++++++++++---
 1 file changed, 12 insertions(+), 3 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 0dfb5faed..110291ebf 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,10 +1,19 @@
-⚠️⚠️⚠️ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
-https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma
+**⚠️ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma**
 
 Tick the checkbox if you understand [x]:
 - [ ] I have read and understand the pull request rules.
 
-# Description
+## **❗ Important: 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.**
+
+- **Reason**: Our current focus is on addressing bugs, improving system performance, and implementing essential updates. This will help stabilize the project and ensure smoother management.
+- **Impact**: While no new feature requests or pull requests are being outright rejected, there may be significant delays in reviews. We encourage the community to help by reviewing PRs or assisting other users in the meantime.
+- **What You Can Do**: If you're interested in contributing, reviewing open PRs or offering support to other users is greatly appreciated. All feature requests and PRs will be revisited once the suspension period is lifted.
+
+We appreciate your patience and understanding as we continue to improve Uptime Kuma.
+
+## Description
 
 Fixes #(issue)
 

From e00f6a4d06eafd3f2fadae0fb81c518ff8a30cca Mon Sep 17 00:00:00 2001
From: GJS <homelab.api@gmail.com>
Date: Wed, 26 Mar 2025 07:42:46 +0100
Subject: [PATCH 07/11] Renamed: Change file name from ask-for-help.yaml to
 ask_for_help.yml

- Renamed the file from `ask-for-help.yaml` to `ask_for_help.yml` to adhere to consistent naming conventions.
- This improves consistency and avoids potential issues with file naming conventions in different environments.

renamed: .github/ISSUE_TEMPLATE/ask-for-help.yaml -> .github/ISSUE_TEMPLATE/ask_for_help.yml
---
 .github/ISSUE_TEMPLATE/{ask-for-help.yaml => ask_for_help.yml} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename .github/ISSUE_TEMPLATE/{ask-for-help.yaml => ask_for_help.yml} (100%)

diff --git a/.github/ISSUE_TEMPLATE/ask-for-help.yaml b/.github/ISSUE_TEMPLATE/ask_for_help.yml
similarity index 100%
rename from .github/ISSUE_TEMPLATE/ask-for-help.yaml
rename to .github/ISSUE_TEMPLATE/ask_for_help.yml

From 3ad2e4b304326f08a0ab5661f676789a76968c2a Mon Sep 17 00:00:00 2001
From: GJS <homelab.api@gmail.com>
Date: Wed, 26 Mar 2025 07:43:07 +0100
Subject: [PATCH 08/11] Renamed and Updated: Rename bug_report.yaml to
 bug_report.yml and adjust label

- Renamed the file `bug_report.yaml` to `bug_report.yml` for consistency with standard YAML file extensions.
- Changed the label from `P2-moderate` to `P2-medium` in the file for better alignment with naming conventions.

renamed: .github/ISSUE_TEMPLATE/bug_report.yaml -> .github/ISSUE_TEMPLATE/bug_report.yml
---
 .github/ISSUE_TEMPLATE/{bug_report.yaml => bug_report.yml} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename .github/ISSUE_TEMPLATE/{bug_report.yaml => bug_report.yml} (99%)

diff --git a/.github/ISSUE_TEMPLATE/bug_report.yaml b/.github/ISSUE_TEMPLATE/bug_report.yml
similarity index 99%
rename from .github/ISSUE_TEMPLATE/bug_report.yaml
rename to .github/ISSUE_TEMPLATE/bug_report.yml
index 6aa8581c5..5d99a2a01 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.yaml
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -2,7 +2,7 @@
 name: "🐛 Bug Report"
 description: "Submit a bug report to help us improve"
 #title: "[Bug] "
-labels: ["bug", "P2-moderate"]
+labels: ["bug", "P2-medium"]
 body:
   - type: "markdown"
     attributes:

From 88e1016fa91274a7590fb963c0a44754867364fc Mon Sep 17 00:00:00 2001
From: GJS <homelab.api@gmail.com>
Date: Wed, 26 Mar 2025 07:43:24 +0100
Subject: [PATCH 09/11] Renamed and Updated: Change file extension and update
 content in feature_request.yml

- Renamed `feature_request.yaml` to `feature_request.yml` to follow project conventions.
- Updated the description in the markdown content to reflect a temporary delay in feature requests and PR reviews.
- Adjusted the labels and body content to better communicate the status of new feature requests.
- Minor revisions in the markdown to enhance clarity and improve the user experience.

renamed: .github/ISSUE_TEMPLATE/feature_request.yaml -> .github/ISSUE_TEMPLATE/feature_request.yml
---
 ...ature_request.yaml => feature_request.yml} | 23 +++++++------------
 1 file changed, 8 insertions(+), 15 deletions(-)
 rename .github/ISSUE_TEMPLATE/{feature_request.yaml => feature_request.yml} (73%)

diff --git a/.github/ISSUE_TEMPLATE/feature_request.yaml b/.github/ISSUE_TEMPLATE/feature_request.yml
similarity index 73%
rename from .github/ISSUE_TEMPLATE/feature_request.yaml
rename to .github/ISSUE_TEMPLATE/feature_request.yml
index 8e3bb020a..5f78f77b5 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.yaml
+++ b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -2,17 +2,20 @@
 name: 🚀 Feature Request
 description: "Submit a proposal for a new feature"
 # title: "[Feature] "
-labels: ["feature-request", "P4-negligible", "backlog"]
+labels: ["feature-request", "P3-low"]
 body:
   - type: "markdown"
     attributes:
       value: |
-        ## **❗ Important: Temporary Suspension of New Feature Requests**
+        ## **❗ Important: Temporary Delay in Feature Requests and Pull Request Reviews**
 
-        **At this time, we are not accepting any new feature requests. Existing feature requests will be moved to the backlog and tagged accordingly.**
+        **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.**
 
-        - **Reason**: Our current priority is focused on fixing bugs, improving system performance, and implementing essential updates. This temporary suspension will allow us to stabilize the project and ensure smoother management.
-        - **What This Means**: During this period, no new feature requests will be reviewed or accepted. However, we continue to welcome feedback, and all suggestions will be reviewed once the suspension is lifted.
+        - **Reason**: Our current focus is on addressing bugs, improving system performance, and implementing essential updates. This will help stabilize the project and ensure smoother management.
+        - **Impact**: While no new feature requests or pull requests are being outright rejected, there may be significant delays in reviews. We encourage the community to help by reviewing PRs or assisting other users in the meantime.
+        - **What You Can Do**: If you're interested in contributing, reviewing open PRs or offering support to other users is greatly appreciated. All feature requests and PRs will be revisited once the suspension period is lifted.
+
+        We appreciate your patience and understanding as we continue to improve Uptime Kuma.
 
         ## **❗ Important: Please Avoid Unnecessary Pinging of Maintainers**
 
@@ -20,16 +23,6 @@ body:
 
         - **Why**: To help maintainers focus on high-priority tasks, we kindly request that unnecessary or repeated pings be minimized. This will help ensure quicker responses for matters that truly need attention.
         - **What This Means**: Non-urgent pings may be ignored or addressed later. Please assess the urgency of your request before pinging a maintainer.
-  - type: checkboxes
-    id: temporary-suspension-of-new-feature-requests
-    attributes:
-      label:
-        "I have read and understand that no new feature requests will be
-        accepted until further notice."
-      options:
-        - label:
-            "I understand that my feature request will be placed in the backlog."
-          required: true
   - type: textarea
     id: related-issues
     validations:

From e1bef33742d04088bb7c392118a8ff96c930c330 Mon Sep 17 00:00:00 2001
From: GJS <homelab.api@gmail.com>
Date: Wed, 26 Mar 2025 08:55:15 +0100
Subject: [PATCH 10/11] New file: Introduce Review Process document for Uptime
 Kuma

- Added a new `REVIEW_PROCESS.md` file outlining the guidelines for reviewing pull requests.
- The document aims to standardize the review process, ensuring consistency and improving code quality.
- It includes sections on preparation, general review, testing, security, performance, compliance, and more.

new file: .github/REVIEW_PROCESS.md
---
 .github/REVIEW_PROCESS.md | 219 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 219 insertions(+)
 create mode 100644 .github/REVIEW_PROCESS.md

diff --git a/.github/REVIEW_PROCESS.md b/.github/REVIEW_PROCESS.md
new file mode 100644
index 000000000..7bebb9e6b
--- /dev/null
+++ b/.github/REVIEW_PROCESS.md
@@ -0,0 +1,219 @@
+# Review Process for Uptime Kuma
+
+**Note:** This Review Process document is a work in progress. Updates and
+improvements are being made, so please check back regularly for the latest
+version.
+
+## Preparation for Reviewing a PR
+
+### Read the PR description carefully
+
+Make sure you understand what the PR is trying to solve or implement. This could
+be a bug fix, a new feature, or a refactor.
+
+### Check the linked issues
+
+If the PR has a linked issue, read it to better understand the context and the
+reason for the change.
+
+### Check the test coverage
+
+Make sure relevant tests have been added or modified. If the PR adds new
+functionality, there should be tests covering the change.
+
+## General Review
+
+### Code formatting and style
+
+Check if the code adheres to the agreed style guidelines of the project (e.g.,
+PEP8 for Python, Airbnb style for JavaScript, etc.). Make sure there are no
+unused imports, variables, or code fragments in the PR.
+
+-   [Project Style](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#project-styles)
+-   [Coding Style](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#coding-styles)
+
+### Readability and maintainability
+
+Is the code understandable to other developers? Ensure that complex parts are
+well-documented with comments. Are variables and functions clearly named, and
+does the code follow a consistent naming convention? Additionally, check if the
+code is maintainable:
+
+-   Is it unnecessarily complex? Could it be simplified?
+-   Does it follow the **[Single Responsibility Principle (SRP)]**?
+
+[Single Responsibility Principle (SRP)]: https://www.geeksforgeeks.org/single-responsibility-in-solid-design-principle/
+
+### Documentation
+
+Is the PR well documented? Check if the descriptions of functions, parameters,
+and return values are present. Are there any changes needed to the README or
+other documentation, for example, if new features or configurations are
+introduced?
+
+## Functional Review
+
+### Testing
+
+Ensure that the new code is properly tested. This includes unit tests,
+integration tests, and if necessary, end-to-end tests.
+
+### Test results
+
+Did all tests pass in the CI pipeline (e.g., GitHub Actions, Travis, CircleCI)?
+
+### Testing in different environments
+
+If the changes depend on certain environments or configurations, verify that the
+code has been tested in various environments (e.g., local development, staging,
+production).
+
+-   [How to test Pull Requests](https://github.com/louislam/uptime-kuma/wiki/Test-Pull-Requests)
+
+### Edge cases and regressions
+
+-   Are there test cases for possible edge cases?
+-   Could this change introduce regressions in other parts of the system?
+
+## Security
+
+### Security issues
+
+Check for potential security problems, such as SQL injection, XSS attacks, or
+unsafe API calls. Are there passwords, tokens, or other sensitive data left in
+the code by mistake?
+
+### Authentication and authorization
+
+Is access to sensitive data or functionality properly secured? Check that the
+correct authorization and authentication mechanisms are in place.
+
+### Security Best Practices
+
+-   Ensure that the code is free from common vulnerabilities like **SQL
+    injection**, **XSS attacks**, and **insecure API calls**.
+-   Check for proper encryption of sensitive data, and ensure that **passwords**
+    or **API tokens** are not hardcoded in the code.
+
+## Performance
+
+### Performance impact
+
+Check if the changes negatively impact performance. This can include factors
+like load times, memory usage, or other performance aspects.
+
+### Use of external libraries
+
+-   Have the right libraries been chosen?
+-   Are there unnecessary dependencies that might reduce performance or increase
+    code complexity?
+-   Are these dependencies actively maintained and free of known vulnerabilities?
+
+### Performance Best Practices
+
+-   **Measure performance** using tools like Lighthouse or profiling libraries.
+-   **Avoid unnecessary dependencies** that may bloat the codebase.
+-   Ensure that the **code does not degrade the user experience** (e.g., by
+    increasing load times or memory consumption).
+
+## Compliance and Integration
+
+### Alignment with the project
+
+Are the changes consistent with the project goals and requirements? Ensure the
+PR aligns with the architecture and design principles of the project.
+
+### Integration
+
+If the PR depends on other PRs or changes, verify that they integrate well with
+the rest of the project. Ensure the code does not cause conflicts with other
+active PRs.
+
+### Backward compatibility
+
+Does the change break compatibility with older versions of the software or
+dependencies? If so, is there a migration plan in place?
+
+## Logging and Error Handling
+
+### Proper error handling
+
+-   Are errors properly caught and handled instead of being silently ignored?
+-   Are exceptions used appropriately?
+
+### Logging
+
+-   Is sufficient logging included for debugging and monitoring?
+-   Is there excessive logging that could affect performance?
+
+## Accessibility (for UI-related changes)
+
+If the PR affects the user interface, ensure that it meets accessibility
+standards:
+
+-   Can users navigate using only the keyboard?
+-   Are screen readers supported?
+-   Is there proper color contrast for readability?
+-   Are there **WCAG** (Web Content Accessibility Guidelines) compliance issues?
+-   Use tools like **Axe** or **Lighthouse** to evaluate accessibility.
+
+## Providing Feedback
+
+### Constructive feedback
+
+Provide clear, constructive feedback on what is good and what can be improved.
+If improvements are needed, be specific about what should change.
+
+### Clarity and collaboration
+
+Ensure your feedback is friendly and open, so the team member who submitted the
+PR feels supported and motivated to make improvements.
+
+## Go/No-Go Decision ━ For Maintainers only
+
+### Go
+
+If the code has no issues and meets the project requirements, approve it (and
+possibly merge it).
+
+### No-Go
+
+If there are significant issues, such as missing tests, security
+vulnerabilities, or performance problems, request the necessary changes before
+the PR can be approved. Some examples of **significant issues** include:
+
+-   Missing tests for new functionality.
+-   Identified **security vulnerabilities**.
+-   Code changes that break **backward compatibility** without a proper migration
+    plan.
+-   Code that causes **major performance regressions** (e.g., high CPU/memory
+    usage).
+
+## After the Review ━ For Maintainers only
+
+### Reordering and merging
+
+Once the necessary changes have been made and the PR is approved, the code can
+be merged into the main branch (e.g., `main` or `master`).
+
+### Testing after merging
+
+Ensure that the build passes after merging the PR, and re-test the functionality
+in the production environment if necessary.
+
+## Follow-up ━ For Maintainers only
+
+### Communication with team members
+
+If the PR has long-term technical or functional implications, communicate the
+changes to the team.
+
+### Monitoring
+
+Continue monitoring the production environment for any unexpected issues that
+may arise after the code has been merged.
+
+---
+
+This process ensures that PRs are systematically and thoroughly reviewed,
+improving overall code quality.

From 284e3ea1596edadbc82447bdf62657e9d3df947b Mon Sep 17 00:00:00 2001
From: GJS <homelab.api@gmail.com>
Date: Wed, 26 Mar 2025 10:29:35 +0100
Subject: [PATCH 11/11] Updated: Revise wording for pull request template

- Reworded the note about pull request acceptance to improve clarity.
- Updated the phrasing to make the message more concise and user-friendly.
- Changed the link text for better accessibility and readability.

modified: .github/PULL_REQUEST_TEMPLATE.md
---
 .github/PULL_REQUEST_TEMPLATE.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 110291ebf..561458d3e 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,6 +1,7 @@
-**⚠️ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma**
+**⚠️ 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)**
+
+Check the box below if you understand [x]:
 
-Tick the checkbox if you understand [x]:
 - [ ] I have read and understand the pull request rules.
 
 ## **❗ Important: Temporary Delay in Feature Requests and Pull Request Reviews**