From 1fa53bc9cc896ab7da9ce2bbe52aee1245c32cae Mon Sep 17 00:00:00 2001 From: Fini Jastrow Date: Sun, 12 Mar 2023 21:57:11 +0100 Subject: [PATCH] Lock closed issues [why] Sometimes people comment on (long) closed issues because they have similar problems. But that is often just a me-too, and all the details to reproduce the issue are missing. [how] Lock old closed issues and add some comment that a new issue should be opened instead. Signed-off-by: Fini Jastrow --- .github/workflows/lock.yml | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 .github/workflows/lock.yml diff --git a/.github/workflows/lock.yml b/.github/workflows/lock.yml new file mode 100644 index 000000000..0fb5bbe4f --- /dev/null +++ b/.github/workflows/lock.yml @@ -0,0 +1,28 @@ +name: 'Lock Threads' + +on: + schedule: + - cron: '0 * * * *' + workflow_dispatch: + +permissions: + issues: write + +concurrency: + group: lock + +jobs: + action: + runs-on: ubuntu-latest + steps: + - uses: dessant/lock-threads@v4 + with: + issue-inactive-days: '182' + issue-comment: > + This issue has been automatically locked since there + has not been any recent activity (i.e. last half year) after it was closed. + It helps our maintainers focus on the active issues. + If you have found a problem that seems similar, please open a new + issue, complete the issue template with all the details + necessary to reproduce, and mention this issue as reference. + process-only: 'issues'