From d88f66b019bb48190a2d662600fd63c26d455f9b Mon Sep 17 00:00:00 2001 From: snipe Date: Wed, 18 Jul 2018 02:57:05 -0700 Subject: [PATCH] Updated to stale.yml --- .github/stale.yml | 23 +++++++++++++++++++++-- 1 file changed, 21 insertions(+), 2 deletions(-) diff --git a/.github/stale.yml b/.github/stale.yml index 991cdf27bd..53acc282e4 100644 --- a/.github/stale.yml +++ b/.github/stale.yml @@ -13,12 +13,31 @@ exemptLabels: - "👩‍💻 ready for dev" - "💰 bounty" - "✋ bug" + +exemptMilestones: true + # Label to use when marking an issue as stale staleLabel: stale + +only: issues + +# Comment to post when removing the stale label. +unmarkComment: > + Okay, it looks like this issue or feature request might still be important. We'll re-open + it for now. Thank you for letting us know! + # Comment to post when marking an issue as stale. Set to `false` to disable markComment: > + Is this still relevant? We haven't heard from anyone in a bit. If so, + please comment with any updates or additional detail. + This issue has been automatically marked as stale because it has not had - recent activity. It will be closed if no further activity occurs. Thank you + recent activity. It will be closed if no further activity occurs. Don't + take it personally, we just need to keep a handle on things. Thank you for your contributions! # Comment to post when closing a stale issue. Set to `false` to disable -closeComment: false +closeComment: > + This issue has been automatically closed because it has not had + recent activity. If you believe this is still an issue, please confirm that + this issue is still happening in the most recent version of Snipe-IT and reply + to this thread to re-open it.