Lock closed issues and PRs workflow (grafana/alloy)
The Lock closed issues and PRs workflow from grafana/alloy, explained and optimized by Latchkey.
A
CI health: A - excellent
Point runs-on at Latchkey and get job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Lock closed issues and PRs workflow from the grafana/alloy repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.
Below, Latchkey shows a faster, safer version produced by its optimization engine.
The workflow
workflow (.yml)
name: Lock closed issues and PRs
on:
workflow_dispatch: {}
schedule:
- cron: '0 0 * * *'
permissions:
issues: write
pull-requests: write
discussions: write
concurrency:
group: lock-threads
jobs:
action:
runs-on: ubuntu-latest
steps:
- uses: dessant/lock-threads@89ae32b08ed1a541efecbab17912962a5e38981c # v6.0.2
with:
pr-inactive-days: 14
issue-inactive-days: 14
add-issue-labels: 'frozen-due-to-age'
add-pr-labels: 'frozen-due-to-age'
process-only: 'issues, prs'
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Lock closed issues and PRs on: workflow_dispatch: {} schedule: - cron: '0 0 * * *' permissions: issues: write pull-requests: write discussions: write concurrency: group: lock-threads jobs: action: timeout-minutes: 30 runs-on: latchkey-small steps: - uses: dessant/lock-threads@89ae32b08ed1a541efecbab17912962a5e38981c # v6.0.2 with: pr-inactive-days: 14 issue-inactive-days: 14 add-issue-labels: 'frozen-due-to-age' add-pr-labels: 'frozen-due-to-age' process-only: 'issues, prs'
What changed
- Run on Latchkey managed runners with one line (
runs-on), which apply the fixes below automatically and self-heal transient failures. This example useslatchkey-small; pick the runner size that fits the job. - Add a job timeout so a hung step cannot burn hours of runner time.
This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.