Star notice workflow (d2-projects/d2-admin)

The Star notice workflow from d2-projects/d2-admin, explained and optimized by Latchkey.

What it does

This is the Star notice workflow from the d2-projects/d2-admin 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: Star notice

on:
  watch:
    types: [started]

jobs:
  bark:

    runs-on: ubuntu-latest

    steps:
    - name: send bark message
      run: |
        repo=${GITHUB_REPOSITORY//\//:}
        actor=$GITHUB_ACTOR
        curl https://api.day.app/B3H8T6rF2p5Mj6z6oha82K/$actor%20star%20了你的仓库/$repo

The same workflow, on Latchkey

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

name: Star notice
 
on:
  watch:
    types: [started]
 
jobs:
  bark:
    timeout-minutes: 30
 
    runs-on: latchkey-small
 
    steps:
    - name: send bark message
      run: |
        repo=${GITHUB_REPOSITORY//\//:}
        actor=$GITHUB_ACTOR
        curl https://api.day.app/B3H8T6rF2p5Mj6z6oha82K/$actor%20star%20了你的仓库/$repo

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.

What Latchkey heals here

This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:

• Network fetches

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