341c8afd76
All checks were successful
check / check (push) Successful in 19s
script/cibuild and script/precommit both existed and were already the documented CI and pre-commit entrypoints, but neither had a Makefile target, so the standing rule to drive the repo through make targets rather than the underlying tool could not be followed for either. It matters most for the build. A bare `docker build .` fails closed on the CHECK_EPOCH guard by design, so script/cibuild is one of only three supported ways to build an image here, and it was the only one of the three without a target while `make docker` had one. The two targets are thin shims in the same style as every other target and change nothing about what the scripts do. .PHONY was already complete for the targets that existed and now lists both new ones. README.md's Entrypoints section gains the script-to-target mapping so the two documents agree, including the two names that do not match: script/install-precommit is `make hooks`, and script/precommit is `make precommit`. It also warns that `make cibuild` runs two container builds and costs minutes, so nobody types it expecting the runtime the other make targets have.
38 lines
400 B
Makefile
38 lines
400 B
Makefile
.PHONY: bootstrap setup test lint fmt fmt-check check docker cibuild precommit hooks serve
|
|
|
|
bootstrap:
|
|
@script/bootstrap
|
|
|
|
setup:
|
|
@script/setup
|
|
|
|
test:
|
|
@script/test
|
|
|
|
lint:
|
|
@script/lint
|
|
|
|
fmt:
|
|
@script/fmt
|
|
|
|
fmt-check:
|
|
@script/fmt-check
|
|
|
|
check:
|
|
@script/check
|
|
|
|
docker:
|
|
@script/docker
|
|
|
|
cibuild:
|
|
@script/cibuild
|
|
|
|
precommit:
|
|
@script/precommit
|
|
|
|
hooks:
|
|
@script/install-precommit
|
|
|
|
serve:
|
|
@hugo server
|