Skip to content

web: comment on rendered HTML too (click an element → line-anchored c… #37

web: comment on rendered HTML too (click an element → line-anchored c…

web: comment on rendered HTML too (click an element → line-anchored c… #37

Workflow file for this run

name: CI
on:
push:
branches: [main]
pull_request:
# pyclawd dogfoods itself: install it + its dev deps, then run the exact same
# `pyclawd check` (format-check -> lint -> typecheck -> test) a developer runs
# locally — across the supported Python matrix. A green local `pyclawd check`
# therefore predicts a green CI.
jobs:
check:
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:
python-version: ["3.10", "3.11", "3.12", "3.13"]
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: ${{ matrix.python-version }}
- run: python -m pip install --upgrade pip
- run: python -m pip install -e ".[dev]"
- name: pyclawd check (dogfood)
run: pyclawd check
# Build the docs the same way a developer does — dogfooding the docs pipeline so
# a broken runner / failing notebook is caught in CI. Needs the isolated docs env
# (./docs) and the pandoc system binary that nbsphinx shells out to.
docs:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: "3.12"
- run: sudo apt-get update && sudo apt-get install -y pandoc
- run: python -m pip install --upgrade pip
- run: python -m pip install -e ".[dev]" -e ./docs
- name: Build pyclawd's own docs (dogfood)
run: pyclawd docs build
- name: Docs-build integration test
run: python -m pytest tests/test_docs_integration.py -c tests/pytest.ini -v