Files
zeekay 6561e62429 ci: drop the GitHub lane, keep its vet step in the native gate
.hanzo/workflows/ exists, so the forge resolves that directory and
.github/workflows/ has not been reachable here. GitHub still executed it,
which is what made the same image buildable from two places.

ci.yaml overlapped the native pair almost entirely: lint-and-vet compiled the
module, and the docker job called hanzoai/.github docker-build.yml to publish
ghcr.io/hanzoai/kafka, which hanzo.yml already declares. The one gate it had
that the pair did not is go vet, now folded into the existing test entry
rather than given a workflow of its own.

Not carried over: staticcheck, which came from dominikh/staticcheck-action;
and the integration-test job, which provisions a PubSub server and the Kafka
CLI to drive a live broker. That job was continue-on-error, so it never
gated a merge, and hanzo.yml already records that the e2e suites belong to a
harness rather than a push gate.

workflow-sanity.yml triggered only on .github/workflows/**, a path that no
longer exists.
2026-08-13 21:03:06 -07:00

16 lines
455 B
YAML

# Go Kafka-protocol broker + client. One image, and a gate that compiles the
# module and runs the offline suites. test/e2e drives a live broker over the
# network, so it belongs to a harness, not a push gate.
images:
- name: kafka
context: .
dockerfile: Dockerfile
repo: ghcr.io/hanzoai/kafka
test:
- name: build-and-unit
run: |
set -euo pipefail
go build ./...
go vet ./...
go test ./protocol/... ./serde/...