jpmschweitzerandClaude
755aa61107
Environment guards now exit 69 rather than 1, so a caller can tell a suite that could not start from one that ran and failed. The first toj test sweep reported "3 repositories failed" and none of the three had executed a test — two could not find go, one had no venv. That points the reader at the tests when the fault is in the environment. Only the environment guards change. A gitleaks finding, a failed test run and a vulncheck hit still exit 1, because those did run and did fail. Co-Authored-By: Claude <noreply@anthropic.com>
31 lines
1.1 KiB
Makefile
31 lines
1.1 KiB
Makefile
# core-api — the repo's command surface (D-27).
|
|
#
|
|
# Paths resolve here rather than in callers (D-10). `python3` on this host is
|
|
# 3.8 and cannot parse these sources, and a bare `pytest` resolves only in a
|
|
# login shell — so both are named explicitly through the venv.
|
|
|
|
VENV := $(CURDIR)/.venv
|
|
PYTHON ?= python3.12
|
|
|
|
.DEFAULT_GOAL := help
|
|
|
|
.PHONY: help
|
|
help: ## Show this help
|
|
@grep -hE '^[a-z][a-z0-9_-]*:.*?## ' $(MAKEFILE_LIST) \
|
|
| awk 'BEGIN{FS=":.*?## "}{printf " \033[36m%-14s\033[0m %s\n", $$1, $$2}'
|
|
|
|
.PHONY: setup
|
|
setup: ## Create the venv and install dependencies
|
|
$(PYTHON) -m venv .venv
|
|
$(VENV)/bin/pip install -r requirements.txt -r dev-requirements.txt
|
|
|
|
.PHONY: test
|
|
test: ## Run the test suite
|
|
@test -x $(VENV)/bin/python || { echo "FAIL — no venv; run: make setup"; exit 69; }
|
|
$(VENV)/bin/python -m pytest tests/
|
|
|
|
# No `lint` target, deliberately. This repo configures no linter — no ruff or
|
|
# flake8 config, and neither in requirements. Per D-27 the name is reserved for
|
|
# repos that lint; an empty target here would report clean for something never
|
|
# run. Add the target when a linter is added, not before.
|