Issue Mark Duplicate workflow (element-plus/element-plus)

The Issue Mark Duplicate workflow from element-plus/element-plus, explained and optimized by Latchkey.

What it does

This is the Issue Mark Duplicate workflow from the element-plus/element-plus 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: Issue Mark Duplicate

on:
  issue_comment:
    types: [created, edited]

permissions:
  issues: write

jobs:
  mark-duplicate:
    runs-on: ubuntu-latest
    steps:
      - name: mark-duplicate
        uses: actions-cool/issues-helper-backup@d65454423c6fbbd20026b9b499d403f79422ac69
        with:
          actions: 'mark-duplicate'
          token: ${{ secrets.GITHUB_TOKEN }}
          close-issue: true

The same workflow, on Latchkey

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

name: Issue Mark Duplicate
 
on:
  issue_comment:
    types: [created, edited]
 
permissions:
  issues: write
 
jobs:
  mark-duplicate:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - name: mark-duplicate
        uses: actions-cool/issues-helper-backup@d65454423c6fbbd20026b9b499d403f79422ac69
        with:
          actions: 'mark-duplicate'
          token: ${{ secrets.GITHUB_TOKEN }}
          close-issue: true
 

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.