AgentScan workflow (babel/babel)
The AgentScan workflow from babel/babel, explained and optimized by Latchkey.
A
CI health: A - excellent
Point runs-on at Latchkey and get job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the AgentScan workflow from the babel/babel 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: AgentScan
on:
pull_request_target:
types:
- opened
- reopened
issues:
types:
- opened
jobs:
agentscan:
runs-on: ubuntu-latest
permissions:
pull-requests: write
issues: write
contents: read
steps:
- name: Cache AgentScan analysis
uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae
with:
path: .agentscan-cache
key: agentscan-cache-${{ github.actor }}
restore-keys: agentscan-cache-
- name: AgentScan
uses: MatteoGabriele/agentscan-action@2b7e598bd821bc0f4651e985688951930c2f60d0
with:
cache-path: ".agentscan-cache"
github-token: ${{ secrets.GITHUB_TOKEN }}
skip-comment-on-organic: true
skip-members: "nicolo-ribaudo,JLHwung,liuxingbaoyu,babel-bot,fisker"
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: AgentScan on: pull_request_target: types: - opened - reopened issues: types: - opened jobs: agentscan: timeout-minutes: 30 runs-on: latchkey-small permissions: pull-requests: write issues: write contents: read steps: - name: Cache AgentScan analysis uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae with: path: .agentscan-cache key: agentscan-cache-${{ github.actor }} restore-keys: agentscan-cache- - name: AgentScan uses: MatteoGabriele/agentscan-action@2b7e598bd821bc0f4651e985688951930c2f60d0 with: cache-path: ".agentscan-cache" github-token: ${{ secrets.GITHUB_TOKEN }} skip-comment-on-organic: true skip-members: "nicolo-ribaudo,JLHwung,liuxingbaoyu,babel-bot,fisker"
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 useslatchkey-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.