From fb8e60f24c049d03da89c9ed61954099fc8d772a Mon Sep 17 00:00:00 2001
From: Erik Huelsmann <ehuels@gmail.com>
Date: Fri, 25 Aug 2023 20:46:17 +0200
Subject: [PATCH] Create no-response.yml

---
 .github/workflows/no-response.yml | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)
 create mode 100644 .github/workflows/no-response.yml

diff --git a/.github/workflows/no-response.yml b/.github/workflows/no-response.yml
new file mode 100644
index 0000000..cb3d82a
--- /dev/null
+++ b/.github/workflows/no-response.yml
@@ -0,0 +1,25 @@
+name: No Response
+
+# Both `issue_comment` and `scheduled` event types are required for this Action
+# to work properly.
+on:
+  issue_comment:
+    types: [created]
+  schedule:
+    # Schedule for five minutes after the hour, every hour
+    - cron: '5 3 * * *'
+
+jobs:
+  noResponse:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: lee-dohm/no-response@v0.5.0
+        with:
+          token: ${{ github.token }}
+          # Number of days of inactivity before an Issue is closed for lack of response
+          daysUntilClose: 90
+          # Label requiring a response
+          responseRequiredLabel: waiting-for-user
+          # Comment to post when closing an Issue for lack of response. Set to `false` to disable
+          closeComment: >
+            Closing: more than 90 days without user response. Feel free to reopen with your comments.