Close Issues workflow (jesseduffield/lazygit)

The Close Issues workflow from jesseduffield/lazygit, explained and optimized by Latchkey.

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.

Grade your own workflow free or run it on Latchkey →

Source: jesseduffield/lazygit.github/workflows/close-issues.ymlLicense MITView source

What it does

This is the Close Issues workflow from the jesseduffield/lazygit repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

workflow (.yml)

name: Close Issues

on:
  issue_comment:
    types: [created]

permissions:
  issues: write

jobs:
  close_issue:
    runs-on: ubuntu-latest
    if: ${{ github.event.issue.pull_request == null && startsWith(github.event.comment.body, '/close') }}
    steps:
      - uses: actions/github-script@v9
        with:
          script: |
            const trustedUsers = ['ChrisMcD1', 'jesseduffield', 'stefanhaller']
            const commenter = context.payload.comment.user.login

            console.log(`Commenter: ${commenter}`)

            if (!trustedUsers.includes(commenter)) {
              console.log(`User ${commenter} is not trusted. Ignoring.`)
              return
            }

            const issueNumber = context.payload.issue.number
            const owner = context.repo.owner
            const repo = context.repo.repo

            await github.rest.issues.update({
              owner,
              repo,
              issue_number: issueNumber,
              state: 'closed'
            })

            console.log(`Closed issue #${issueNumber} by request from ${commenter}.`)

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: Close Issues
 
on:
  issue_comment:
    types: [created]
 
permissions:
  issues: write
 
jobs:
  close_issue:
    timeout-minutes: 30
    runs-on: latchkey-small
    if: ${{ github.event.issue.pull_request == null && startsWith(github.event.comment.body, '/close') }}
    steps:
      - uses: actions/github-script@v9
        with:
          script: |
            const trustedUsers = ['ChrisMcD1', 'jesseduffield', 'stefanhaller']
            const commenter = context.payload.comment.user.login
 
            console.log(`Commenter: ${commenter}`)
 
            if (!trustedUsers.includes(commenter)) {
              console.log(`User ${commenter} is not trusted. Ignoring.`)
              return
            }
 
            const issueNumber = context.payload.issue.number
            const owner = context.repo.owner
            const repo = context.repo.repo
 
            await github.rest.issues.update({
              owner,
              repo,
              issue_number: issueNumber,
              state: 'closed'
            })
 
            console.log(`Closed issue #${issueNumber} by request from ${commenter}.`)

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 uses latchkey-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.

Actions used in this workflow

actions/github-script