Skip to content
Latchkey

Ping triage on issue create workflow (MithrilJS/mithril.js)

The Ping triage on issue create workflow from MithrilJS/mithril.js, explained and optimized by Latchkey.

B

CI health: B - good

Run this on Latchkey for self-healing, caching, and up to 58% lower cost.

Grade your own workflow free or run it on Latchkey →
Source: MithrilJS/mithril.js.github/workflows/issue-create.ymlLicense MITView source

What it does

This is the Ping triage on issue create workflow from the MithrilJS/mithril.js 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: Ping triage on issue create
on:
  issues:
    types: [opened]
  pull_request_target:
    types: [opened]
jobs:
  notify_triage:
    uses: MithrilJS/infra/.github/workflows/notify-triage.yml@main
    secrets: inherit

The same workflow, on Latchkey

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

name: Ping triage on issue create
on:
  issues:
    types: [opened]
  pull_request_target:
    types: [opened]
jobs:
  notify_triage:
    timeout-minutes: 30
    uses: MithrilJS/infra/.github/workflows/notify-triage.yml@main
    secrets: inherit
 

What changed

1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.