From 447bd481f2874629ddc4a8e9b469f75f5ad20217 Mon Sep 17 00:00:00 2001 From: Jon Barker Date: Wed, 19 Jul 2023 14:53:21 -0700 Subject: [PATCH] Remove auto-closing in stale bot --- .github/workflows/stale.yml | 7 ++----- CONTRIBUTING.md | 2 +- 2 files changed, 3 insertions(+), 6 deletions(-) diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml index 27c6d525ef..3c6932d412 100644 --- a/.github/workflows/stale.yml +++ b/.github/workflows/stale.yml @@ -22,11 +22,8 @@ jobs: with: repo-token: ${{ secrets.GITHUB_TOKEN }} days-before-stale: 60 - days-before-issue-close: 21 - stale-issue-message: 'Marking as stale. No activity in 60 days. Remove stale label or comment or this will be closed in 21 days.' - stale-pr-message: 'Marking as stale. No activity in 60 days. Remove stale label or comment or this will be closed in 21 days.' - close-issue-message: 'No activity on stale issue in 21 days.' - close-pr-message: 'No activity on stale PR in 21 days.' + stale-issue-message: 'Marking as stale. No activity in 60 days.' + stale-pr-message: 'Marking as stale. No activity in 60 days.' stale-issue-label: 'stale' stale-pr-label: 'stale' remove-stale-when-updated: true diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 221aa69c66..615227600c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -59,7 +59,7 @@ The corresponding maintainers at this time are @jaredcasper and @jon-barker. ### Is there a policy for issues and PRs that haven't been touched in X days? Should they be closed? -Yes, starting in July 2023 we have a bot that will mark untouched PRs as "stale" after 60 days, and close them after another 21 days if nothing happens. If you think an issue/PR should be re-opened or requires additional attention at that point then ping a maintainer. +Yes, starting in July 2023 we have a bot that will mark untouched PRs as "stale" after 60 days. We have a long backlog of issues and PRs dating back 3.5 years. We are trying to triage these now by working backwards. Older issues we believe may still be relevant may recieve a request to re-test them with the latest code. If there's no response they may be closed. Again, if you they should be re-opened then just respond with a comment to that effect.