From fe723b8ca7813b9d791936b006a94b2f9950ab3d Mon Sep 17 00:00:00 2001 From: surchs Date: Tue, 5 Sep 2023 17:18:23 +0000 Subject: [PATCH] =?UTF-8?q?=F0=9F=94=84=20synced=20local=20'.github/workfl?= =?UTF-8?q?ows/'=20with=20remote=20'template=5Fworkflows/'?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .github/workflows/stale.yml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml index 52d92bb..e4565fe 100644 --- a/.github/workflows/stale.yml +++ b/.github/workflows/stale.yml @@ -11,8 +11,14 @@ jobs: with: stale-issue-message: | We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 30 days. - We have applied the stale-issue label to indicate that this issue should be reviewed again and then either prioritized or closed. + We have applied the `_flag:stale` label to indicate that this issue should be reviewed again. + When you review, please reread the spec and then apply one of these three options: + - prioritize: apply the `flag:schedule` label to suggest moving this issue into the backlog now + - close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close. + - archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case + apply the `someday` label to show that this won't be prioritized. The stalebot will ignore issues with this + label in the future. Use sparingly! days-before-stale: 30 days-before-close: -1 - stale-issue-label: '@ flag:stale' + stale-issue-label: '_flag:stale' exempt-issue-labels: ['Roadmap', 'Milestone', 'Epic', 'someday']