Steffen Becker
64cc010f01
The parity findings named the six files the corpus is built from, so every measurement carried a document title into the history. They move to a gitignored FINDINGS.md beside the corpus itself; the README keeps the harness. A test that needs a document builds one, so nothing under src/ or tests/ reads the gitignored corpus — CI greps for exactly that.
27 lines
869 B
YAML
27 lines
869 B
YAML
name: CI
|
|
|
|
on:
|
|
push:
|
|
branches: [main]
|
|
pull_request:
|
|
|
|
jobs:
|
|
check-and-test:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
# CLAUDE.md is read at every session start; detail belongs in the nested files.
|
|
- run: test "$(wc -l < CLAUDE.md)" -le 120 || { echo "CLAUDE.md over its 120-line budget"; exit 1; }
|
|
# The corpus is gitignored, so a test reading it would name a document and fail here.
|
|
- run: |
|
|
! git grep -l "render-parity/fixtures" -- src tests ':!tests/render-parity' \
|
|
|| { echo "a test reads the gitignored parity corpus"; exit 1; }
|
|
- uses: actions/setup-node@v4
|
|
with:
|
|
node-version: 20
|
|
cache: npm
|
|
- run: npm ci
|
|
- run: npm run check
|
|
# LibreOffice is not installed here, so the lo-roundtrip suite self-skips.
|
|
- run: npm test
|