Skip to content
Latchkey

Docs deploy workflow (bdfinst/agentic-dev-team)

The Docs deploy workflow from bdfinst/agentic-dev-team, explained and optimized by Latchkey.

D

CI health: D - needs work

Point runs-on at Latchkey and get caching, run de-duplication, job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →
Source: bdfinst/agentic-dev-team.github/workflows/docs.ymlLicense MITView source

What it does

This is the Docs deploy workflow from the bdfinst/agentic-dev-team 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: Docs deploy

on:
  push:
    branches: [main]
    paths:
      - "**.md"
      - mkdocs.yml
      - requirements-docs.txt
      - scripts/assemble-docs.sh
      - .github/workflows/docs.yml
  workflow_dispatch:

permissions:
  contents: write

jobs:
  deploy:
    name: Deploy docs site
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
        with:
          fetch-depth: 0

      - uses: actions/setup-python@v6
        with:
          python-version: "3.x"

      - name: Install MkDocs dependencies
        run: pip install -r requirements-docs.txt

      - name: Assemble docs sources
        run: bash scripts/assemble-docs.sh

      - name: Build and deploy to GitHub Pages
        run: mkdocs gh-deploy --force --no-history

The same workflow, on Latchkey

Estimated ~20% faster on cache hits, plus fewer wasted runs and a safer supply chain. Added and changed lines are highlighted.

name: Docs deploy
 
on:
  push:
    branches: [main]
    paths:
      - "**.md"
      - mkdocs.yml
      - requirements-docs.txt
      - scripts/assemble-docs.sh
      - .github/workflows/docs.yml
  workflow_dispatch:
 
permissions:
  contents: write
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  deploy:
    timeout-minutes: 30
    name: Deploy docs site
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v7
        with:
          fetch-depth: 0
 
      - uses: actions/setup-python@v6
        with:
          cache: 'pip'
          python-version: "3.x"
 
      - name: Install MkDocs dependencies
        run: pip install -r requirements-docs.txt
 
      - name: Assemble docs sources
        run: bash scripts/assemble-docs.sh
 
      - name: Build and deploy to GitHub Pages
        run: mkdocs gh-deploy --force --no-history
 

What changed

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:

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