Issues Similarity Analysis workflow (Johnserf-Seed/f2)

The Issues Similarity Analysis workflow from Johnserf-Seed/f2, 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: Johnserf-Seed/f2.github/workflows/issue_similarity.ymlLicense Apache-2.0View source

What it does

This is the Issues Similarity Analysis workflow from the Johnserf-Seed/f2 repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

workflow (.yml)

name: Issues Similarity Analysis

on:
  issues:
    types: [opened, edited]

permissions:
  issues: write

jobs:
  similarity-analysis:
    runs-on: ubuntu-latest
    steps:
      - name: analysis
        uses: actions-cool/issues-similarity-analysis@v1.3.2
        with:
          filter-threshold: 0.5
          comment-title: '### Similarity Issues'
          comment-body: '${index}. ${similarity} #${number}'
          show-footer: false
          show-mentioned: true
          since-days: 730

The same workflow, on Latchkey

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

name: Issues Similarity Analysis
 
on:
  issues:
    types: [opened, edited]
 
permissions:
  issues: write
 
jobs:
  similarity-analysis:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - name: analysis
        uses: actions-cool/issues-similarity-analysis@v1.3.2
        with:
          filter-threshold: 0.5
          comment-title: '### Similarity Issues'
          comment-body: '${index}. ${similarity} #${number}'
          show-footer: false
          show-mentioned: true
          since-days: 730

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.