From c50cdd62706ed00a2bb9e1201ac8aac1b71e9a16 Mon Sep 17 00:00:00 2001
From: dundargoc <33953936+dundargoc@users.noreply.github.com>
Date: Thu, 27 Apr 2023 22:07:44 +0200
Subject: ci: replace stale bot with custom implementation

The stale action has a bug where it won't close an issue/PR if it has
comments after the stale label.
---
 .github/scripts/close_unresponsive.js | 50 +++++++++++++++++++++++++++++++++++
 1 file changed, 50 insertions(+)
 create mode 100644 .github/scripts/close_unresponsive.js

(limited to '.github/scripts/close_unresponsive.js')

diff --git a/.github/scripts/close_unresponsive.js b/.github/scripts/close_unresponsive.js
new file mode 100644
index 0000000000..b7a92207ba
--- /dev/null
+++ b/.github/scripts/close_unresponsive.js
@@ -0,0 +1,50 @@
+function labeledEvent(data) {
+  return data.event === "labeled" && data.label.name === "needs:response";
+}
+
+const numberOfDaysLimit = 30;
+const close_message = `This has been closed since a request for information has \
+not been answered for ${numberOfDaysLimit} days. It can be reopened when the \
+requested information is provided.`;
+
+module.exports = async ({ github, context }) => {
+  const owner = context.repo.owner;
+  const repo = context.repo.repo;
+
+  const issues = await github.rest.issues.listForRepo({
+    owner: owner,
+    repo: repo,
+    labels: "needs:response",
+  });
+  const numbers = issues.data.map((e) => e.number);
+
+  for (const number of numbers) {
+    const timeline = await github.rest.issues.listEventsForTimeline({
+      owner: owner,
+      repo: repo,
+      issue_number: number,
+    });
+    const data = timeline.data.filter(labeledEvent);
+    const latest_response_label = data[data.length - 1];
+    const created_at = new Date(latest_response_label.created_at);
+    const now = new Date();
+    const diff = now - created_at;
+    const diffDays = diff / (1000 * 60 * 60 * 24);
+
+    if (diffDays > numberOfDaysLimit) {
+      github.rest.issues.update({
+        owner: owner,
+        repo: repo,
+        issue_number: number,
+        state: "closed",
+      });
+
+      github.rest.issues.createComment({
+        owner: owner,
+        repo: repo,
+        issue_number: number,
+        body: close_message,
+      });
+    }
+  }
+};
-- 
cgit 


From 1cbfed03c249e7f9e67d59566fbabe46f7f7f1f9 Mon Sep 17 00:00:00 2001
From: dundargoc <33953936+dundargoc@users.noreply.github.com>
Date: Sun, 7 May 2023 16:46:24 +0200
Subject: ci(response): use pagination for timeline events

GitHub paginates responses with many results, which needs to be taken
into account as the number of events in an issue can be large.
---
 .github/scripts/close_unresponsive.js | 19 ++++++++++++-------
 1 file changed, 12 insertions(+), 7 deletions(-)

(limited to '.github/scripts/close_unresponsive.js')

diff --git a/.github/scripts/close_unresponsive.js b/.github/scripts/close_unresponsive.js
index b7a92207ba..f0e8bbe93e 100644
--- a/.github/scripts/close_unresponsive.js
+++ b/.github/scripts/close_unresponsive.js
@@ -19,13 +19,18 @@ module.exports = async ({ github, context }) => {
   const numbers = issues.data.map((e) => e.number);
 
   for (const number of numbers) {
-    const timeline = await github.rest.issues.listEventsForTimeline({
-      owner: owner,
-      repo: repo,
-      issue_number: number,
-    });
-    const data = timeline.data.filter(labeledEvent);
-    const latest_response_label = data[data.length - 1];
+    const events = await github.paginate(
+      github.rest.issues.listEventsForTimeline,
+      {
+        owner: owner,
+        repo: repo,
+        issue_number: number,
+      },
+      (response) => response.data.filter(labeledEvent)
+    );
+
+    const latest_response_label = events[events.length - 1];
+
     const created_at = new Date(latest_response_label.created_at);
     const now = new Date();
     const diff = now - created_at;
-- 
cgit