From cf2d603e277d18e96906ac36743ec4e7d58b8aad Mon Sep 17 00:00:00 2001
From: Frank Elsinga <frank@elsinga.de>
Date: Wed, 14 Feb 2024 06:43:31 +0100
Subject: [PATCH] `Stale`, incorrect issue template and `cannot-reproduce`
 Comments (#4490)

---
 .github/workflows/stale-bot.yml | 28 ++++++++++++++++++++++++----
 extra/close-incorrect-issue.js  |  2 +-
 2 files changed, 25 insertions(+), 5 deletions(-)

diff --git a/.github/workflows/stale-bot.yml b/.github/workflows/stale-bot.yml
index 4d1cd93ec..6acd303fb 100644
--- a/.github/workflows/stale-bot.yml
+++ b/.github/workflows/stale-bot.yml
@@ -11,12 +11,32 @@ jobs:
     steps:
       - uses: actions/stale@v8
         with:
-          stale-issue-message: 'We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.'
-          close-issue-message: 'This issue was closed because it has been stalled for 2 days with no activity.'
-          days-before-stale: 90
-          days-before-close: 2
+          stale-issue-message: |-
+            We are clearing up our old `help`-issues and your issue has been open for 60 days with no activity.
+            If no comment is made and the stale label is not removed, this issue will be closed in 7 days.
+          days-before-stale: 60
+          days-before-close: 7
           days-before-pr-stale: -1
           days-before-pr-close: -1
           exempt-issue-labels: 'News,Medium,High,discussion,bug,doc,feature-request'
           exempt-issue-assignees: 'louislam'
           operations-per-run: 200
+      - uses: actions/stale@v8
+        with:
+          stale-issue-message: |-
+            This issue was marked as `cannot-reproduce` by a maintainer.
+            If an issue is non-reproducible, we cannot fix it, as we do not know what the underlying issue is.
+            If you have any ideas how we can reproduce this issue, we would love to hear them.
+            
+            We don't have a good way to deal with truely unreproducible issues and are going to close this issue in a month.
+            If think there might be other differences in our environment or in how we tried to reproduce this, we would appreciate any ideas.
+          close-issue-message: |-
+            This issue will be closed as no way to reproduce it has been found.
+            If you/somebody finds a way how to (semi-reliably) reproduce this, we can reopen this issue. ^^
+          days-before-stale: 180
+          days-before-close: 30
+          days-before-pr-stale: -1
+          days-before-pr-close: -1
+          any-of-issue-labels: 'cannot-reproduce'
+          operations-per-run: 200
+    
diff --git a/extra/close-incorrect-issue.js b/extra/close-incorrect-issue.js
index ae38bccc2..9bb01b19d 100644
--- a/extra/close-incorrect-issue.js
+++ b/extra/close-incorrect-issue.js
@@ -37,7 +37,7 @@ const github = require("@actions/github");
                 owner: issue.owner,
                 repo: issue.repo,
                 issue_number: issue.number,
-                body: `@${username}: Hello! :wave:\n\nThis issue is being automatically closed because it does not follow the issue template. Please DO NOT open a blank issue.`
+                body: `@${username}: Hello! :wave:\n\nThis issue is being automatically closed because it does not follow the issue template. Please **DO NOT open blank issues and use our [issue-templates](https://github.com/louislam/uptime-kuma/issues/new/choose) instead**.\nBlank Issues do not contain the context nessesary for a good discussions.`
             });
 
             // Close the issue