Closed issue comment workflow (Textualize/textual)

The Closed issue comment workflow from Textualize/textual, 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: Textualize/textual.github/workflows/comment.ymlLicense MITView source

What it does

This is the Closed issue comment workflow from the Textualize/textual 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: Closed issue comment
on:
  issues:
    types: [closed]

jobs:
  add-comment:
    runs-on: ubuntu-latest
    permissions:
      issues: write
    steps:
      - name: Did I help?
        uses: peter-evans/create-or-update-comment@a35cf36e5301d70b76f316e867e7788a55a31dae
        with:
          issue-number: ${{ github.event.issue.number }}
          body: |
            I hope I solved your issue!
            
            Consider [sponsoring my work](https://github.com/sponsors/willmcgugan) to continue to maintain and develop Textual.
            
            - Will McGugan

The same workflow, on Latchkey

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

name: Closed issue comment
on:
  issues:
    types: [closed]
 
jobs:
  add-comment:
    timeout-minutes: 30
    runs-on: latchkey-small
    permissions:
      issues: write
    steps:
      - name: Did I help?
        uses: peter-evans/create-or-update-comment@a35cf36e5301d70b76f316e867e7788a55a31dae
        with:
          issue-number: ${{ github.event.issue.number }}
          body: |
            I hope I solved your issue!
            
            Consider [sponsoring my work](https://github.com/sponsors/willmcgugan) to continue to maintain and develop Textual.
            
            - Will McGugan

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

peter-evans/create-or-update-comment