Greetings workflow (runesleo/x-reader)

The Greetings workflow from runesleo/x-reader, 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: runesleo/x-reader.github/workflows/greetings.ymlLicense MITView source

What it does

This is the Greetings workflow from the runesleo/x-reader 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: Greetings

on:
  pull_request_target:
    types: [opened]
  issues:
    types: [opened]

jobs:
  greeting:
    runs-on: ubuntu-latest
    permissions:
      issues: write
      pull-requests: write
    steps:
    - uses: actions/first-interaction@v1
      with:
        repo-token: ${{ secrets.GITHUB_TOKEN }}
        issue-message: "👋 Welcome! Thank you for opening your first issue in X-Reader. The maintainers will look into it as soon as possible."
        pr-message: "🎉 Thank you for opening your first pull request! We appreciate your contribution to X-Reader."

The same workflow, on Latchkey

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

name: Greetings
 
on:
  pull_request_target:
    types: [opened]
  issues:
    types: [opened]
 
jobs:
  greeting:
    timeout-minutes: 30
    runs-on: latchkey-small
    permissions:
      issues: write
      pull-requests: write
    steps:
    - uses: actions/first-interaction@v1
      with:
        repo-token: ${{ secrets.GITHUB_TOKEN }}
        issue-message: "👋 Welcome! Thank you for opening your first issue in X-Reader. The maintainers will look into it as soon as possible."
        pr-message: "🎉 Thank you for opening your first pull request! We appreciate your contribution to X-Reader."

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.