mirror of
https://github.com/vercel/next.js.git
synced 2026-09-20 02:25:18 +08:00
Sebastian "Sebbie" Silbermann
52cd5b96ab
The last remaining `Lock Threads` failures are likely due to missing permissions for discussions which `dessant/lock-threads` handles by default. This disables discussion handling to get the workflow green to start tracking regressions. We can discuss if we want to lock inactive discussions in a follow-up (which would be new behavior this workflow never performed). Co-authored-by: Claude Code (kimi-k3[1m]) <noreply@anthropic.com>
33 lines
1.0 KiB
YAML
33 lines
1.0 KiB
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@89ae32b08ed1a541efecbab17912962a5e38981c # v6.0.2
|
|
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
|
|
# The token has no `discussions` permission and discussions are not
|
|
# meant to be locked, so skip them (they are processed by default).
|
|
process-only: 'issues, prs'
|