From 8dbf45a65a360de844e4f5c95b8c1541bddb5bfd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mikkel=20Hjortsh=C3=B8j?= Date: Sun, 24 Jul 2022 23:54:39 +0200 Subject: [PATCH 1/4] Update stale.yml --- .github/workflows/stale.yml | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml index fb20c73de..99f597305 100644 --- a/.github/workflows/stale.yml +++ b/.github/workflows/stale.yml @@ -26,7 +26,18 @@ jobs: The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.. + stale-pr-message: | + Hello! + + I am marking this PR as stale as it has not received any engagement from the community or maintainers 120 days. That does not imply that the issue has no merit! If you feel strongly about this issue + - leave a comment on it and discuss ideas how you could contribute towards resolving it; + - leave a comment and describe in detail why this issue is critical for your use case; + + The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.. + stale-issue-label: "stale" days-before-stale: 120 - days-before-close: 30 + days-before-close: 100 exempt-draft-pr: true + ascending: true + operations-per-run: 250 From cb0273b5d7fd70ec667d927c4440e84eadfd4b30 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mikkel=20Hjortsh=C3=B8j?= Date: Sun, 24 Jul 2022 23:58:43 +0200 Subject: [PATCH 2/4] Update stale.yml --- .github/workflows/stale.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml index 99f597305..bded3ebc7 100644 --- a/.github/workflows/stale.yml +++ b/.github/workflows/stale.yml @@ -40,4 +40,4 @@ jobs: days-before-close: 100 exempt-draft-pr: true ascending: true - operations-per-run: 250 + operations-per-run: 1000 From b02e42c6dc6cad63d09b8ec43c66ac6884bba771 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mikkel=20Hjortsh=C3=B8j?= Date: Mon, 25 Jul 2022 00:05:36 +0200 Subject: [PATCH 3/4] Update stale.yml --- .github/workflows/stale.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml index bded3ebc7..185f9658c 100644 --- a/.github/workflows/stale.yml +++ b/.github/workflows/stale.yml @@ -2,7 +2,7 @@ name: "Close Stale Issues & PRs" on: workflow_dispatch: schedule: - - cron: "0 0 * * *" + - cron: "0 21 * * *" permissions: issues: write @@ -41,3 +41,4 @@ jobs: exempt-draft-pr: true ascending: true operations-per-run: 1000 + exempt-issue-labels: "ignore" From a9f744cb6459e82d3790fc007caf95f30e5b8535 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mikkel=20Hjortsh=C3=B8j?= Date: Mon, 25 Jul 2022 00:07:29 +0200 Subject: [PATCH 4/4] Update stale.yml --- .github/workflows/stale.yml | 39 ++++++++++++++++++------------------- 1 file changed, 19 insertions(+), 20 deletions(-) diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml index 185f9658c..ea97be064 100644 --- a/.github/workflows/stale.yml +++ b/.github/workflows/stale.yml @@ -15,27 +15,26 @@ jobs: - name: Close Stale Issues uses: actions/stale@v5.1.0 with: - stale-issue-message: | - Hello! - - I am marking this issue as stale as it has not received any engagement from the community or maintainers 120 days. That does not imply that the issue has no merit! If you feel strongly about this issue - - open a PR referencing and resolving the issue; - - leave a comment on it and discuss ideas how you could contribute towards resolving it; - - leave a comment and describe in detail why this issue is critical for your use case; - - open a new issue with updated details and a plan on resolving the issue. +# stale-issue-message: | +# Hello! +# +# I am marking this issue as stale as it has not received any engagement from the community or maintainers 120 days. That does not imply that the issue has no merit! If you feel strongly about this issue +# - open a PR referencing and resolving the issue; +# - leave a comment on it and discuss ideas how you could contribute towards resolving it; +# - leave a comment and describe in detail why this issue is critical for your use case; +# - open a new issue with updated details and a plan on resolving the issue. +# +# The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.. +# +# stale-pr-message: | +# Hello! +# +# I am marking this PR as stale as it has not received any engagement from the community or maintainers 120 days. That does not imply that the issue has no merit! If you feel strongly about this issue +# - leave a comment on it and discuss ideas how you could contribute towards resolving it; +# - leave a comment and describe in detail why this issue is critical for your use case; +# +# The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.. - The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.. - - stale-pr-message: | - Hello! - - I am marking this PR as stale as it has not received any engagement from the community or maintainers 120 days. That does not imply that the issue has no merit! If you feel strongly about this issue - - leave a comment on it and discuss ideas how you could contribute towards resolving it; - - leave a comment and describe in detail why this issue is critical for your use case; - - The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.. - - stale-issue-label: "stale" days-before-stale: 120 days-before-close: 100 exempt-draft-pr: true