issues workflow (dooit-org/dooit)

The issues workflow from dooit-org/dooit, explained and optimized by Latchkey.

What it does

This is the issues workflow from the dooit-org/dooit 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

name: issues
on:
  issues:
    types: [closed]
jobs:
  add-comment:
    runs-on: ubuntu-latest
    permissions:
      issues: write
    steps:
      - name: Did we solve your problem?
        uses: peter-evans/create-or-update-comment@a35cf36e5301d70b76f316e867e7788a55a31dae
        with:
          issue-number: ${{ github.event.issue.number }}
          body: |
            Did we solve your problem?
            Glad we could help! 
            
            Consider sponsoring my work through [github sponsors](https://github.com/sponsors/kraanzu) :smile:
            – @kraanzu

The same workflow, on Latchkey

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

name: issues
on:
  issues:
    types: [closed]
jobs:
  add-comment:
    timeout-minutes: 30
    runs-on: latchkey-small
    permissions:
      issues: write
    steps:
      - name: Did we solve your problem?
        uses: peter-evans/create-or-update-comment@a35cf36e5301d70b76f316e867e7788a55a31dae
        with:
          issue-number: ${{ github.event.issue.number }}
          body: |
            Did we solve your problem?
            Glad we could help! 
            
            Consider sponsoring my work through [github sponsors](https://github.com/sponsors/kraanzu) :smile:
            – @kraanzu
 

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