Skip to content

Add lock-threads workflow - #247

Merged
mishamyte merged 1 commit into
devfrom
ci/lock-threads
Jul 25, 2026
Merged

Add lock-threads workflow#247
mishamyte merged 1 commit into
devfrom
ci/lock-threads

Conversation

@mishamyte

Copy link
Copy Markdown
Collaborator

Mirrors the Lock threads workflow from the Unleashed firmware repo.

Closed issues and PRs get locked after 14 days of inactivity, so stale threads stop accumulating "me too" / necro comments that never reach a maintainer. Locking is not closing - it only stops new comments, nothing is auto-closed, and anyone can still open a fresh issue from the templates.

  • Runs daily at 03:00 UTC, plus workflow_dispatch for manual sweeps
  • issues: write / pull-requests: write only; no checkout, no code execution
  • concurrency group so a manual run and the nightly cron cannot overlap
  • Lock reason resolved on both issues and PRs
  • dessant/lock-threads@v6 (current major, latest release v6.0.2)

The only difference from the Unleashed copy is the comment wording: this tracker is per-app, so it asks people to name the affected app instead of pointing at a firmware version.

The existing backlog (169 closed issues + 69 closed/merged PRs) has already been locked with reason resolved and no comment, so this workflow's first run has nothing to back-fill and will not comment on any old thread.

🤖 Generated with Claude Code

Lock closed issues and PRs after 14 days of inactivity, matching the
setup in the Unleashed firmware repo. Runs daily at 03:00 UTC and can
be kicked off by hand via workflow_dispatch.

Locking is not closing: it only stops new comments on already-closed
threads, and anyone can still open a fresh issue from the templates.
The bot comment is reworded for this repo - it asks people to name the
app they are hitting the problem in, since this tracker is per-app.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@mishamyte
mishamyte merged commit 4fbaea7 into dev Jul 25, 2026
2 checks passed
@mishamyte
mishamyte deleted the ci/lock-threads branch July 25, 2026 21:53
@mishamyte mishamyte self-assigned this Jul 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant