summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDave Davenport <qball@gmpclient.org>2024-03-15 10:29:04 +0100
committerDave Davenport <qball@gmpclient.org>2024-03-15 10:29:04 +0100
commit94f8c88336fcfe81bd9c51dcd9628add8b34aeca (patch)
tree0a618d6c992fa80d2c8071f4c70ea76ef5529457
parent81e06d715786219c66d20289e17cd8867ecee70c (diff)
[github] update lock config.
-rw-r--r--.github/workflows/lock.yml47
1 files changed, 28 insertions, 19 deletions
diff --git a/.github/workflows/lock.yml b/.github/workflows/lock.yml
index fdc2a319..2636ca10 100644
--- a/.github/workflows/lock.yml
+++ b/.github/workflows/lock.yml
@@ -1,32 +1,41 @@
-name: 'Lock threads'
+name: 'Lock Threads'
on:
schedule:
- cron: '0 0 * * *'
+ workflow_dispatch:
+
+permissions:
+ issues: write
+ pull-requests: write
+ discussions: write
+
+concurrency:
+ group: lock-threads
jobs:
- lock:
+ action:
runs-on: ubuntu-latest
steps:
- uses: dessant/lock-threads@v5
with:
- github-token: ${{ secrets.GITHUB_TOKEN }}
- issue-lock-inactive-days: '31'
- issue-exclude-created-before: ''
- issue-exclude-labels: ''
- issue-lock-labels: ''
- issue-lock-reason: 'resolved'
- issue-lock-comment: >
- This issue has been automatically locked since there
- has not been any recent activity after it was closed.
- Please open a new issue for related bugs.
- pr-lock-inactive-days: '31'
- pr-exclude-created-before: ''
- pr-exclude-labels: ''
- pr-lock-labels: ''
- pr-lock-reason: 'resolved'
- pr-lock-comment: >
+ process-only: 'issues'
+ github-token: ${{ github.token }}
+ issue-inactive-days: '31'
+ exclude-issue-created-before: ''
+ exclude-issue-created-after: ''
+ exclude-issue-created-between: ''
+ exclude-issue-closed-before: ''
+ exclude-issue-closed-after: ''
+ exclude-issue-closed-between: ''
+ include-any-issue-labels: ''
+ include-all-issue-labels: ''
+ exclude-any-issue-labels: ''
+ add-issue-labels: ''
+ remove-issue-labels: ''
+ issue-comment: >
This pull request has been automatically locked since there
has not been any recent activity after it was closed.
Please open a new issue for related bugs.
- process-only: ''
+ issue-lock-reason: 'resolved'
+ log-output: false