Pull Request workflow (asacristani/fastapi-rocket-boilerplate)

The Pull Request workflow from asacristani/fastapi-rocket-boilerplate, explained and optimized by Latchkey.

What it does

This is the Pull Request workflow from the asacristani/fastapi-rocket-boilerplate 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: Pull Request
on: [pull_request]
concurrency:
  group: ${{ github.head_ref || github.run_id }}
  cancel-in-progress: true

permissions: read-all

jobs:
  trunk_check:
    name: Trunk Check Runner
    runs-on: ubuntu-latest
    permissions:
      checks: write # For trunk to post annotations
      contents: read # For repo checkout

    steps:
      - name: Checkout
        uses: actions/checkout@v3

      - name: Trunk Check
        uses: trunk-io/trunk-action@v1

The same workflow, on Latchkey

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

name: Pull Request
on: [pull_request]
concurrency:
  group: ${{ github.head_ref || github.run_id }}
  cancel-in-progress: true
 
permissions: read-all
 
jobs:
  trunk_check:
    timeout-minutes: 30
    name: Trunk Check Runner
    runs-on: latchkey-small
    permissions:
      checks: write # For trunk to post annotations
      contents: read # For repo checkout
 
    steps:
      - name: Checkout
        uses: actions/checkout@v3
 
      - name: Trunk Check
        uses: trunk-io/trunk-action@v1
 

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.

Actions used in this workflow