Deploy docs to GitHub Pages workflow (bootstrap-vue/bootstrap-vue)
The Deploy docs to GitHub Pages workflow from bootstrap-vue/bootstrap-vue, explained and optimized by Latchkey.
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 Deploy docs to GitHub Pages workflow from the bootstrap-vue/bootstrap-vue 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 docs to GitHub Pages
on:
push:
branches:
- master
- dev
# Allows you to run this workflow manually from the Actions tab
workflow_dispatch:
# Sets permissions of the "GITHUB_TOKEN" to allow deployment to GitHub Pages
permissions:
contents: read
pages: write
id-token: write
# Allow only one concurrent deployment, skipping runs queued between the run in-progress
# and latest queued. However, do NOT cancel in-progress runs as we want to allow these
# production deployments to complete.
concurrency:
group: "pages"
cancel-in-progress: false
jobs:
# Build
build:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Setup Node
uses: actions/setup-node@v4
with:
node-version: "20"
cache: "yarn"
- name: Setup Pages
uses: actions/configure-pages@v5
- name: Restore cache
uses: actions/cache@v4
with:
path: |
dist
.nuxt
key: ${{ runner.os }}-nuxt-build-${{ hashFiles('dist') }}
restore-keys: |
${{ runner.os }}-nuxt-build-
- name: Install dependencies
run: yarn install --check-files --frozen-lockfile --non-interactive
- name: Static HTML export with Nuxt
run: yarn docs-gen
- name: Upload artifact
uses: actions/upload-pages-artifact@v3
with:
path: ./docs-dist
# Deploy
deploy:
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
runs-on: ubuntu-latest
needs: build
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v4
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Deploy docs to GitHub Pages on: push: branches: - master - dev # Allows you to run this workflow manually from the Actions tab workflow_dispatch: # Sets permissions of the "GITHUB_TOKEN" to allow deployment to GitHub Pages permissions: contents: read pages: write id-token: write # Allow only one concurrent deployment, skipping runs queued between the run in-progress # and latest queued. However, do NOT cancel in-progress runs as we want to allow these # production deployments to complete. concurrency: group: "pages" cancel-in-progress: false jobs: # Build build: timeout-minutes: 30 runs-on: latchkey-small steps: - name: Checkout uses: actions/checkout@v4 - name: Setup Node uses: actions/setup-node@v4 with: node-version: "20" cache: "yarn" - name: Setup Pages uses: actions/configure-pages@v5 - name: Restore cache uses: actions/cache@v4 with: path: | dist .nuxt key: ${{ runner.os }}-nuxt-build-${{ hashFiles('dist') }} restore-keys: | ${{ runner.os }}-nuxt-build- - name: Install dependencies run: yarn install --check-files --frozen-lockfile --non-interactive - name: Static HTML export with Nuxt run: yarn docs-gen - name: Upload artifact uses: actions/upload-pages-artifact@v3 with: path: ./docs-dist # Deploy deploy: timeout-minutes: 30 environment: name: github-pages url: ${{ steps.deployment.outputs.page_url }} runs-on: latchkey-small needs: build steps: - name: Deploy to GitHub Pages id: deployment uses: actions/deploy-pages@v4
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.
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 2 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.