Skip to content

test: trace the harness's numbers to one run, and seed the admin at volume #375

test: trace the harness's numbers to one run, and seed the admin at volume

test: trace the harness's numbers to one run, and seed the admin at volume #375

Workflow file for this run

---
name: docs
"on":
push:
branches: [main]
pull_request:
workflow_dispatch:
permissions:
contents: read # to fetch code (actions/checkout)
jobs:
build:
name: build docs site
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
- name: Install uv
uses: astral-sh/setup-uv@20cfd1bf945f4377ade1205e4dbc17946fc9a30d # v10.0.1
- name: Build site
run: uv run zensical build
- name: Upload Pages artifact
if: >-
${{ github.event_name == 'workflow_dispatch'
|| (github.event_name == 'push' && github.ref == 'refs/heads/main') }}
# yamllint disable-line rule:line-length
uses: actions/upload-pages-artifact@fc324d3547104276b827a68afc52ff2a11cc49c9 # v5.0.0
with:
path: site
deploy:
name: deploy to GitHub Pages
if: >-
${{ github.event_name == 'workflow_dispatch'
|| (github.event_name == 'push' && github.ref == 'refs/heads/main') }}
needs: build
runs-on: ubuntu-latest
concurrency:
# One deployment at a time; never cancel one in progress. Scoped to this job
# because only it touches Pages — a workflow-level group would also serialize
# every pull request's build behind it, and `build docs site` is a required
# check, so one wedged deployment blocks every merge in the repository.
group: pages
cancel-in-progress: false
permissions:
pages: write # to deploy to Pages
id-token: write # to verify the deploy originates from this workflow
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@cd2ce8fcbc39b97be8ca5fce6e763baed58fa128 # v5.0.0