GitHub Releases to Discord workflow (wizarrrr/wizarr)

The GitHub Releases to Discord workflow from wizarrrr/wizarr, explained and optimized by Latchkey.

CI health: B - good

Point runs-on at Latchkey and get job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →

Source: wizarrrr/wizarr.github/workflows/github-releases-to-discord.ymlLicense MITView source

What it does

This is the GitHub Releases to Discord workflow from the wizarrrr/wizarr 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: GitHub Releases to Discord

on:
  release:
    types: [published]
  workflow_dispatch:
    inputs:
      release_name:
        description: Release title to post
        required: true
      release_body:
        description: Release notes body to post
        required: true
      release_html_url:
        description: Release URL to link in Discord
        required: false

permissions:
  contents: read

jobs:
  github-releases-to-discord:
    name: Notify Discord
    runs-on: ubuntu-latest
    if: github.repository_owner == 'wizarrrr'

    steps:
      - name: Send release notes to Discord
        uses: SethCohen/github-releases-to-discord@v1
        with:
          webhook_url: ${{ secrets.WEBHOOK_URL }}
          username: Wizarr Releases
          footer_title: Changelog
          footer_timestamp: "true"
          reduce_headings: "true"
          release_name: ${{ inputs.release_name }}
          release_body: ${{ inputs.release_body }}
          release_html_url: ${{ inputs.release_html_url }}

The same workflow, on Latchkey

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

name: GitHub Releases to Discord
 
on:
  release:
    types: [published]
  workflow_dispatch:
    inputs:
      release_name:
        description: Release title to post
        required: true
      release_body:
        description: Release notes body to post
        required: true
      release_html_url:
        description: Release URL to link in Discord
        required: false
 
permissions:
  contents: read
 
jobs:
  github-releases-to-discord:
    timeout-minutes: 30
    name: Notify Discord
    runs-on: latchkey-small
    if: github.repository_owner == 'wizarrrr'
 
    steps:
      - name: Send release notes to Discord
        uses: SethCohen/github-releases-to-discord@v1
        with:
          webhook_url: ${{ secrets.WEBHOOK_URL }}
          username: Wizarr Releases
          footer_title: Changelog
          footer_timestamp: "true"
          reduce_headings: "true"
          release_name: ${{ inputs.release_name }}
          release_body: ${{ inputs.release_body }}
          release_html_url: ${{ inputs.release_html_url }}

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.

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.