1240cda484
### Why? They used the `node16` runner which is deprecated ### Notable breaking changes #### `dessant/lock-threads@v5` [link](https://github.com/dessant/lock-threads) Now also locks discussions (in addition to issues and pull requests): https://github.com/dessant/lock-threads/blob/main/CHANGELOG.md#500-2023-11-14 #### `actions/stale@v9` [link](https://github.com/actions/stale) Is now stateful: If the action ends because of [operations-per-run](https://github.com/actions/stale#operations-per-run) then the next run will start from the first unprocessed issue skipping the issues processed during the previous run(s). https://github.com/actions/stale/releases/tag/v9.0.0 Closes PACK-2347 Co-authored-by: Tobias Koppers <tobias.koppers@googlemail.com>
29 lines
823 B
YAML
29 lines
823 B
YAML
name: 'Lock Threads'
|
|
|
|
on:
|
|
schedule:
|
|
# This runs twice a day: https://crontab.guru/#0_0,12_*_*_*
|
|
- cron: '0 0,12 * * *'
|
|
workflow_dispatch:
|
|
|
|
permissions:
|
|
issues: write
|
|
pull-requests: write
|
|
|
|
concurrency:
|
|
group: lock
|
|
|
|
jobs:
|
|
action:
|
|
runs-on: ubuntu-latest
|
|
if: github.repository_owner == 'vercel'
|
|
steps:
|
|
- uses: dessant/lock-threads@v5
|
|
with:
|
|
github-token: ${{ secrets.GITHUB_TOKEN }}
|
|
add-issue-labels: 'locked'
|
|
add-pr-labels: 'locked'
|
|
issue-inactive-days: 14
|
|
issue-comment: 'This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.'
|
|
pr-inactive-days: 14
|
|
log-output: true
|