From 4df8a11f5682239969f0bd38c0495789eecbdeb3 Mon Sep 17 00:00:00 2001 From: Jeremy Herve Date: Wed, 22 Jan 2025 16:21:24 +0100 Subject: [PATCH] Stale bot: trigger stale issues a bit earlier We'll gradually try to address stale issues faster. Let's move from 720 days to 540 days for now, and then we'll reduce it again until we can get to 180. --- .github/workflows/mark-issue-stale.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/mark-issue-stale.yml b/.github/workflows/mark-issue-stale.yml index eddb91180ca7f..3965fb305fb93 100644 --- a/.github/workflows/mark-issue-stale.yml +++ b/.github/workflows/mark-issue-stale.yml @@ -15,9 +15,9 @@ jobs: with: repo-token: ${{ secrets.GITHUB_TOKEN }} # Message to be added to stale issues. - stale-issue-message: 'This issue is stale because 720 days have passed with no activity. A member of the Dotcom Product Ambassadors Guild will review and if required close this issue within 7 days. If you disagree and would like this issue to remain open, please provide additional context, updated reproduction steps and/or screenshots.' + stale-issue-message: 'This issue is stale because 540 days have passed with no activity. A member of the Dotcom Product Ambassadors Guild will review and if required close this issue within 7 days. If you disagree and would like this issue to remain open, please provide additional context, updated reproduction steps and/or screenshots.' # Days before issue is considered stale. - days-before-issue-stale: 720 + days-before-issue-stale: 540 # Override stale setting for PRs. days-before-pr-stale: -1 # Exempted issue labels.