From 56fefd0c4be65e88d76830026052c94d4ade81df Mon Sep 17 00:00:00 2001 From: Julian Date: Fri, 10 Nov 2023 01:50:39 +1100 Subject: [PATCH] Slow down no-response bot (#8443) Fourteen days isn't very long to respond to a request for more information, especially given it may come in weeks, months or years after the original request. Vacations last longer than time. Development crunches last longer than that. Let's give them 6 weeks before the bot gets upset. [I am preparing to share this script across Kivy projects.] --- .github/workflows/no-response.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/no-response.yml b/.github/workflows/no-response.yml index 2b0ba6e2c..f34d06413 100644 --- a/.github/workflows/no-response.yml +++ b/.github/workflows/no-response.yml @@ -20,7 +20,7 @@ jobs: # done by `github-actions[bot]` as the `no-response` Action needs to be compiled. with: token: ${{ github.token }} - daysUntilClose: 14 + daysUntilClose: 42 responseRequiredLabel: 'awaiting-reply' closeComment: > This issue has been automatically closed because there has been no response