From f6ed5eb0649fafb69ee4e7af1e4450bb229d9f96 Mon Sep 17 00:00:00 2001 From: Laurent Date: Sat, 8 Jan 2022 21:51:28 +0000 Subject: [PATCH] Update close-stale-issues.yml --- .github/workflows/close-stale-issues.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/close-stale-issues.yml b/.github/workflows/close-stale-issues.yml index f68a82f927..8d8cf876f8 100644 --- a/.github/workflows/close-stale-issues.yml +++ b/.github/workflows/close-stale-issues.yml @@ -1,7 +1,7 @@ name: 'Close stale issues' on: schedule: - - cron: '0 16 * * *' + - cron: '0 */6 * * *' permissions: issues: write jobs: @@ -15,6 +15,7 @@ jobs: stale-issue-message: "Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions." days-before-stale: 30 days-before-close: 7 + operations-per-run: 1000 exempt-issue-labels: 'good first issue,upstream,backlog,high,medium,spec,cannot reproduce' stale-issue-label: 'stale' close-issue-message: 'Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.'