From 8ebb0fcbe70b1259ef3bb18282594ad59a8ae784 Mon Sep 17 00:00:00 2001 From: Jannis Leidel Date: Thu, 16 Nov 2023 11:09:29 +0100 Subject: [PATCH 1/4] Lower lockbot timeframe and add comment. Resolves #849. --- .github/workflows/lock.yml | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/.github/workflows/lock.yml b/.github/workflows/lock.yml index a1cf48bd..089d2400 100644 --- a/.github/workflows/lock.yml +++ b/.github/workflows/lock.yml @@ -21,7 +21,7 @@ jobs: - uses: dessant/lock-threads@v4 with: # Number of days of inactivity before a closed issue is locked - issue-inactive-days: 365 + issue-inactive-days: 30 # Do not lock issues created before a given timestamp, value must follow ISO 8601 exclude-issue-created-before: '' # Do not lock issues with these labels, value must be a comma separated list of labels or '' @@ -30,7 +30,15 @@ jobs: add-issue-labels: locked # Reason for locking an issue, value must be one of resolved, off-topic, too heated, spam or '' issue-lock-reason: resolved + # Comment to post before locking an issue + issue-comment: > +Hi there, thank you for your contribution to conda! +This issue has been automatically locked since it has not had recent activity after it was closed. Please open a new issue for related bugs. + +If this was a feature request and you think it has merit, please open a new issue referencing and summarizing the previous discussion, along with the required action items. + +Thank you! # Number of days of inactivity before a closed pull request is locked pr-inactive-days: 365 # Do not lock pull requests created before a given timestamp, value must follow ISO 8601 From 7837731861c5616f822aa7d6e2f2d3f259a905e4 Mon Sep 17 00:00:00 2001 From: Jannis Leidel Date: Thu, 16 Nov 2023 11:14:05 +0100 Subject: [PATCH 2/4] Yaml! --- .github/workflows/lock.yml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/.github/workflows/lock.yml b/.github/workflows/lock.yml index 089d2400..8491c7b6 100644 --- a/.github/workflows/lock.yml +++ b/.github/workflows/lock.yml @@ -32,13 +32,13 @@ jobs: issue-lock-reason: resolved # Comment to post before locking an issue issue-comment: > -Hi there, thank you for your contribution to conda! - -This issue has been automatically locked since it has not had recent activity after it was closed. Please open a new issue for related bugs. - -If this was a feature request and you think it has merit, please open a new issue referencing and summarizing the previous discussion, along with the required action items. - -Thank you! + Hi there, thank you for your contribution to conda! + + This issue has been automatically locked since it has not had recent activity after it was closed. Please open a new issue for related bugs. + + If this was a feature request and you think it has merit, please open a new issue referencing and summarizing the previous discussion, along with the required action items. + + Thank you! # Number of days of inactivity before a closed pull request is locked pr-inactive-days: 365 # Do not lock pull requests created before a given timestamp, value must follow ISO 8601 From c4d404f9c58814fa0d2535735f731b2fd61c3a99 Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Thu, 16 Nov 2023 10:14:11 +0000 Subject: [PATCH 3/4] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- .github/workflows/lock.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/lock.yml b/.github/workflows/lock.yml index 8491c7b6..f65bd84b 100644 --- a/.github/workflows/lock.yml +++ b/.github/workflows/lock.yml @@ -33,11 +33,11 @@ jobs: # Comment to post before locking an issue issue-comment: > Hi there, thank you for your contribution to conda! - + This issue has been automatically locked since it has not had recent activity after it was closed. Please open a new issue for related bugs. - + If this was a feature request and you think it has merit, please open a new issue referencing and summarizing the previous discussion, along with the required action items. - + Thank you! # Number of days of inactivity before a closed pull request is locked pr-inactive-days: 365 From d5f3f8786848f727878c6736773835bc8dfaeafa Mon Sep 17 00:00:00 2001 From: Jannis Leidel Date: Wed, 14 Aug 2024 14:12:23 +0200 Subject: [PATCH 4/4] Update to 6 months. --- .github/workflows/lock.yml | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/.github/workflows/lock.yml b/.github/workflows/lock.yml index f65bd84b..330ee6d8 100644 --- a/.github/workflows/lock.yml +++ b/.github/workflows/lock.yml @@ -21,7 +21,7 @@ jobs: - uses: dessant/lock-threads@v4 with: # Number of days of inactivity before a closed issue is locked - issue-inactive-days: 30 + issue-inactive-days: 180 # Do not lock issues created before a given timestamp, value must follow ISO 8601 exclude-issue-created-before: '' # Do not lock issues with these labels, value must be a comma separated list of labels or '' @@ -30,15 +30,6 @@ jobs: add-issue-labels: locked # Reason for locking an issue, value must be one of resolved, off-topic, too heated, spam or '' issue-lock-reason: resolved - # Comment to post before locking an issue - issue-comment: > - Hi there, thank you for your contribution to conda! - - This issue has been automatically locked since it has not had recent activity after it was closed. Please open a new issue for related bugs. - - If this was a feature request and you think it has merit, please open a new issue referencing and summarizing the previous discussion, along with the required action items. - - Thank you! # Number of days of inactivity before a closed pull request is locked pr-inactive-days: 365 # Do not lock pull requests created before a given timestamp, value must follow ISO 8601