Skip to content
Latchkey

pull_request workflow (facebook/jscodeshift)

The pull_request workflow from facebook/jscodeshift, explained and optimized by Latchkey.

C

CI health: C - fair

Run this on Latchkey for self-healing, caching, and up to 58% lower cost.

Grade your own workflow free or run it on Latchkey →
Source: facebook/jscodeshift.github/workflows/pull_request.ymlLicense MITView source

What it does

This is the pull_request workflow from the facebook/jscodeshift 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: pull_request

on:
  pull_request:
    branches: [main]

jobs:
  call-test:
    uses: ./.github/workflows/test.yml

The same workflow, on Latchkey

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

name: pull_request
 
on:
  pull_request:
    branches: [main]
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  call-test:
    timeout-minutes: 30
    uses: ./.github/workflows/test.yml
 

What changed

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