Files
zeekay f81bbf5565 the pipelines this repository actually has
18 inherited workflows described a project this fork is not: nightly cluster
deploys, Jepsen, LDBC, load and systest suites, arm64 matrices and upgrade runs
against versions of a binary nothing here builds. On a push they would run
against code whose worker, conn and raftwal packages no longer exist.

They are replaced by the house pattern: a root `hanzo.yml` naming what CI does
and a cicd.yml that imports hanzoai/ci. There is no image, because this is a Go
library — a published binary would be a second answer to how the engine runs, and
the answer is that a host embeds it.

The ignore file listed build outputs of that same absent binary.
2026-08-20 23:45:25 -07:00

10 lines
359 B
YAML

# What CI builds and tests here, read by both GitHub Actions and platform.hanzo.ai.
#
# There is no image: this repository is a Go library, so `test` is the whole of
# it. A published binary would be a second answer to the question of how the
# engine runs, and the answer is that a host embeds it.
test:
- go build ./...
- go vet ./...
- go test ./...