clawbot
593c97ca50
check / check (push) Successful in 3m24s
make css now runs the Tailwind v4.2.1 standalone CLI in a docker build stage, the binary pinned by sha256, instead of whatever tailwindcss is on the host. A css-check stage, run by make check and required by the image build, fails when static/css/tailwind.css differs from what make css generates. input.css now names its sources (the templates, app.js, and the Go file that picks status colour classes) instead of letting Tailwind scan the whole checkout, where words in Go code and docs became unused classes. .btn-text is removed and tailwind.css regenerated; it only loses unused rules. Model: opus-5-5
16 lines
426 B
Bash
Executable File
16 lines
426 B
Bash
Executable File
#!/bin/sh
|
|
# script/css: regenerate static/css/tailwind.css (writes). tailwindcss is
|
|
# never installed locally: it runs in docker, at the version and sha256
|
|
# pinned in the Dockerfile's stylesheet stages, which also say what the
|
|
# stylesheet is generated from.
|
|
set -eu
|
|
|
|
ROOT="$(cd "$(dirname "$0")/.." && pwd -P)"
|
|
|
|
main() {
|
|
cd "$ROOT"
|
|
docker build --target css-output --output type=local,dest=static/css .
|
|
}
|
|
|
|
main "$@"
|