Deploy Site workflow (wenzhixin/bootstrap-table)
The Deploy Site workflow from wenzhixin/bootstrap-table, explained and optimized by Latchkey.
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.
What it does
This is the Deploy Site workflow from the wenzhixin/bootstrap-table 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: Deploy Site
on:
push:
branches:
- master
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 24
cache: 'yarn'
- name: Build page with Astro
run: |
cd ${{ github.workspace }}/site
yarn install --frozen-lockfile
yarn build
# Disable Jekyll, otherwise _astro folder will be ignored
touch dist/.nojekyll
- name: Upload to Algolia
run: |
cd ${{ github.workspace }}/site
yarn install --frozen-lockfile
ALGOLIA_APP_ID="${{ secrets.ALGOLIA_APP_ID || 'FXDJ517Z8G' }}" \
ALGOLIA_API_KEY="${{ secrets.ALGOLIA_API_KEY }}" \
ALGOLIA_INDEX_NAME="${{ secrets.ALGOLIA_INDEX_NAME || 'bootstrap-table' }}" \
yarn algolia
- name: Checkout gh-pages branch
uses: actions/checkout@v4
with:
ref: 'gh-pages'
path: './gh-pages'
- name: Move versions to target folder
run: |
mv gh-pages/versions site/dist
rm -rf gh-pages
- name: Deploy to GitHub Pages
uses: JamesIves/github-pages-deploy-action@v4
with:
branch: gh-pages
folder: site/dist
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Deploy Site on: push: branches: - master concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: deploy: timeout-minutes: 30 runs-on: latchkey-small steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: 24 cache: 'yarn' - name: Build page with Astro run: | cd ${{ github.workspace }}/site yarn install --frozen-lockfile yarn build # Disable Jekyll, otherwise _astro folder will be ignored touch dist/.nojekyll - name: Upload to Algolia run: | cd ${{ github.workspace }}/site yarn install --frozen-lockfile ALGOLIA_APP_ID="${{ secrets.ALGOLIA_APP_ID || 'FXDJ517Z8G' }}" \ ALGOLIA_API_KEY="${{ secrets.ALGOLIA_API_KEY }}" \ ALGOLIA_INDEX_NAME="${{ secrets.ALGOLIA_INDEX_NAME || 'bootstrap-table' }}" \ yarn algolia - name: Checkout gh-pages branch uses: actions/checkout@v4 with: ref: 'gh-pages' path: './gh-pages' - name: Move versions to target folder run: | mv gh-pages/versions site/dist rm -rf gh-pages - name: Deploy to GitHub Pages uses: JamesIves/github-pages-deploy-action@v4 with: branch: gh-pages folder: site/dist
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. - Cancel superseded runs when a branch or PR gets a newer push.
- 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.
What Latchkey heals here
This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:
- Dependency installs
This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.