Files
pad/Makefile
T
xarmian 21e8ca6a20 chore(make): add make check mirroring CI lint + test + web build (IDEA-921) (#322)
* chore(make): add `make check` mirroring CI lint + test + web build (IDEA-921)

Closes the local-vs-CI gap that let PR #321 ship a trivial gofmt
violation past every step of CONVE-190's pre-flight (`go build &&
go test && cd web && npm run build`).

- `make lint` now runs the same golangci-lint v2.11.4 suite CI runs
  (govet, ineffassign, staticcheck SA*, unused, plus the gofmt
  formatter with simplify: true). The bootstrap rule auto-installs
  the pinned binary into $(go env GOPATH)/bin on first run, so
  contributors don't need a separate setup step.

- `make check` is a new umbrella target that runs lint, the Go test
  suite, and the web build — the exact set of jobs CI's "Go" and
  "Web" jobs run. Run it before pushing.

- `make install` is unchanged (build + restart) so the inner dev loop
  stays fast. `check` is the opt-in pre-push gate.

CONVE-190 updated separately via the Pad CLI to point contributors at
`make check` instead of the old three-command list.

Verified locally: `make check` passes on a clean tree (after a one-
time `golangci-lint cache clean` to clear stale entries from a prior
run — that's a known golangci-lint quirk, not a workflow bug).

* fix(make): enforce lint version pin + cover full CI surface (round 1)

Codex review on PR #322 round 1 surfaced two real gaps in the
make check / make lint plumbing.

1. Makefile:83 — `lint` did not actually enforce GOLANGCI_LINT_VERSION.
   The previous file-target dependency only fired the install rule
   when the binary was missing, so an older or newer locally-installed
   golangci-lint was silently reused, defeating the pin. The recipe
   now compares the installed version against the pin and reinstalls
   on mismatch.

2. Makefile:97 — `check` claimed to mirror CI's Go and Web jobs but
   omitted Web's `npm run check` (svelte-check type checking) and the
   Go job's `govulncheck` step. CI could fail on either while local
   `make check` passed. Added new `vuln` (pinned to GOVULNCHECK_VERSION
   = v1.2.0, matches CI) and `web-check` targets, both wired into
   `make check`.

`make check` now runs: lint + go test + govulncheck + npm ci + npm
audit + npm run build + svelte-check — exactly mirroring the gates
the CI Go and Web jobs use to fail a PR. The race-detector and
PostgreSQL jobs only run on push to main and are intentionally not
part of `make check` (run `make test-pg` separately if needed).

Verified locally: `make check` exits 0; `make lint` correctly no-ops
when the pinned version is already installed.
2026-04-30 16:32:40 -04:00

130 lines
4.7 KiB
Makefile

.PHONY: build test test-pg test-pg-down dev clean web dev-web serve restart lint install check vuln web-check
BINARY=pad
BUILD_DIR=./cmd/pad
HOST?=127.0.0.1
INSTALL_DIR?=$(HOME)/.local/bin
VERSION ?= dev
COMMIT := $(shell git rev-parse --short HEAD 2>/dev/null)
BUILD_TIME := $(shell date -u +%Y-%m-%dT%H:%M:%SZ)
LDFLAGS := -X main.version=$(VERSION) -X main.commit=$(COMMIT) -X main.buildTime=$(BUILD_TIME)
# Pin to the same golangci-lint and govulncheck versions CI runs (see
# .github/workflows/ci.yml). Bump these and CI together when upgrading.
GOLANGCI_LINT_VERSION ?= v2.11.4
GOLANGCI_LINT := $(shell go env GOPATH)/bin/golangci-lint
GOVULNCHECK_VERSION ?= v1.2.0
GOVULNCHECK := $(shell go env GOPATH)/bin/govulncheck
build: web
go build -ldflags "$(LDFLAGS)" -o $(BINARY) $(BUILD_DIR)
build-go:
go build -ldflags "$(LDFLAGS)" -o $(BINARY) $(BUILD_DIR)
install: build
@# Stop running server, install binary, clear stale pid.
@# CAUTION: `killall -9 pad` is SYSTEM-WIDE. If another user (or another
@# project on the same machine) is also running a `pad` process, it will
@# get killed too. Designed for single-developer local setups; don't run
@# `make install` on a shared host.
-killall -9 $(BINARY) 2>/dev/null
@sleep 1
@mkdir -p $(INSTALL_DIR)
cp -f $(BINARY) $(INSTALL_DIR)/$(BINARY)
rm -f ~/.pad/pad.pid
@echo "Installed $(BINARY) to $(INSTALL_DIR)/$(BINARY)"
@# Trigger server auto-start by running a command
@$(INSTALL_DIR)/$(BINARY) auth whoami 2>/dev/null || true
@echo "Server restarted."
test:
go test ./... -v
# Run tests against PostgreSQL (starts a container automatically).
# Uses port 5445 to avoid conflicts with any local PostgreSQL.
test-pg:
docker compose -f docker-compose.test.yml up -d --wait
PAD_TEST_POSTGRES_URL="postgres://pad:pad@localhost:5445/pad?sslmode=disable" go test ./... -v -count=1; \
EXIT_CODE=$$?; \
docker compose -f docker-compose.test.yml down -v; \
exit $$EXIT_CODE
test-pg-down:
docker compose -f docker-compose.test.yml down -v
dev: build-go
./$(BINARY) server start --host $(HOST)
serve: build
-./$(BINARY) server stop 2>/dev/null
@sleep 1
./$(BINARY) server start --host $(HOST)
restart: build-go
-./$(BINARY) server stop 2>/dev/null
@sleep 1
./$(BINARY) server start --host $(HOST)
web:
cd web && npm ci && npm run build
dev-web:
cd web && npm run dev
clean:
rm -f $(BINARY)
rm -rf web/build
go clean ./...
# Run the same golangci-lint suite CI runs (.golangci.yml: govet,
# ineffassign, staticcheck SA*, unused, plus the gofmt formatter with
# simplify: true). The lint suite already includes go vet via the govet
# linter, so we don't double-run it here.
#
# Version enforcement: the recipe checks the installed binary against
# GOLANGCI_LINT_VERSION and reinstalls on mismatch. A file-target
# dependency wouldn't enforce the pin — make only runs the install rule
# when the binary is missing, so an outdated local binary would be
# silently reused and disagree with CI (Codex review on PR #322).
lint:
@bin="$(GOLANGCI_LINT)"; pin="$(GOLANGCI_LINT_VERSION)"; want="$${pin#v}"; \
have=$$( $$bin version 2>/dev/null | sed -n 's/.*version \([0-9.]*\) built.*/\1/p' ); \
if [ "$$have" != "$$want" ]; then \
echo "Installing golangci-lint $$pin (had: $${have:-none})..."; \
go install github.com/golangci/golangci-lint/v2/cmd/golangci-lint@$$pin; \
fi
$(GOLANGCI_LINT) run --timeout=5m ./...
# Run govulncheck against the call graph. Mirrors the "Run govulncheck"
# step in CI's Go job verbatim. `go install foo@vX.Y.Z` is idempotent
# and rebuilds quickly when the pinned version is already in the module
# cache, so we don't need a version-check shim like lint has.
vuln:
go install golang.org/x/vuln/cmd/govulncheck@$(GOVULNCHECK_VERSION)
$(GOVULNCHECK) ./...
# Web pre-flight that mirrors CI's Web job beyond the build step:
# `npm audit` (production dependencies, high severity+) and svelte-check
# type checking. Depends on `web` so npm ci + build are already done.
# Separate target so a contributor iterating on the UI can run just the
# extra checks via `make web-check`.
web-check: web
cd web && npm audit --audit-level=high --omit=dev && npm run check
# Pre-flight target that mirrors CI's Go and Web jobs. Run this before
# pushing — if it passes, the corresponding CI checks should pass too.
#
# Covers: golangci-lint suite (lint), Go test suite, govulncheck, npm ci,
# npm audit, web build, svelte-check. The race-detector + Postgres jobs
# only run on push to main (per .github/workflows/ci.yml) and are not
# included here; run `make test-pg` separately if you want them locally.
#
# `make install` stays lightweight (build + restart only) so the inner
# dev loop is fast; opt into `check` when you're ready to push.
check: lint
go test ./...
$(MAKE) vuln
$(MAKE) web-check