Skip to content
Latchkey

Release PR workflow (beautifier/js-beautify)

The Release PR workflow from beautifier/js-beautify, explained and optimized by Latchkey.

C

CI health: C - fair

Point runs-on at Latchkey and get run de-duplication, 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: beautifier/js-beautify.github/workflows/pr-staging.ymlLicense MITView source

What it does

This is the Release PR workflow from the beautifier/js-beautify 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)
# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
# For more information see: https://help.github.com/actions/language-and-framework-guides/publishing-nodejs-packages

name: Release PR

on:
  push:
    branches:
      - 'staging/gh-pages'
      - 'staging/main'
      - 'staging/release'


jobs:
  PR-from-staging:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
        with:
          fetch-depth: 0
      - name: pull-request gh-pages
        if: github.ref == 'refs/heads/staging/gh-pages'
        uses: repo-sync/pull-request@v2
        with:
          pr_title: "Pulling staging/gh-pages into gh-pages"
          source_branch: "staging/gh-pages"
          destination_branch: "gh-pages"
          github_token: ${{ secrets.GITHUB_TOKEN }}
      - name: pull-request main
        if: github.ref == 'refs/heads/staging/main'
        uses: repo-sync/pull-request@v2
        with:
          pr_title: "Pulling staging/main into main"
          source_branch: "staging/main"
          destination_branch: "main"
          github_token: ${{ secrets.GITHUB_TOKEN }}
      - name: pull-request release
        if: github.ref == 'refs/heads/staging/release'
        uses: repo-sync/pull-request@v2
        with:
          pr_title: "Pulling staging/release into release"
          source_branch: "staging/release"
          destination_branch: "release"
          github_token: ${{ secrets.GITHUB_TOKEN }}

The same workflow, on Latchkey

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

# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
# For more information see: https://help.github.com/actions/language-and-framework-guides/publishing-nodejs-packages
 
name: Release PR
 
on:
  push:
    branches:
      - 'staging/gh-pages'
      - 'staging/main'
      - 'staging/release'
 
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  PR-from-staging:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v7
        with:
          fetch-depth: 0
      - name: pull-request gh-pages
        if: github.ref == 'refs/heads/staging/gh-pages'
        uses: repo-sync/pull-request@v2
        with:
          pr_title: "Pulling staging/gh-pages into gh-pages"
          source_branch: "staging/gh-pages"
          destination_branch: "gh-pages"
          github_token: ${{ secrets.GITHUB_TOKEN }}
      - name: pull-request main
        if: github.ref == 'refs/heads/staging/main'
        uses: repo-sync/pull-request@v2
        with:
          pr_title: "Pulling staging/main into main"
          source_branch: "staging/main"
          destination_branch: "main"
          github_token: ${{ secrets.GITHUB_TOKEN }}
      - name: pull-request release
        if: github.ref == 'refs/heads/staging/release'
        uses: repo-sync/pull-request@v2
        with:
          pr_title: "Pulling staging/release into release"
          source_branch: "staging/release"
          destination_branch: "release"
          github_token: ${{ secrets.GITHUB_TOKEN }}
 

What changed

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.

Actions used in this workflow