Files
zeekay 16a8e5dc97 run the unit suite instead of answering issue comments
The one workflow here replied to labels and comments on GitHub issues and pull
requests by calling hanzoai/ide. Those events are GitHub's, and the reusable it
called reaches api.github.com for the pull request it edits, so there is
nothing to port. The @hanzo-agent macro on issues goes with it.

What was never running is tests/unit — file validation, history, results,
workspace root. It runs now on every push and pull request. tests/integration
stays out: it drives a real editor against a workspace on disk, which is a
harness, not a push.
2026-08-13 21:07:59 -07:00

24 lines
913 B
YAML

# Canonical CI/CD config for hanzoai/aci — read by the hanzoai/ci reusable
# (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
#
# No `images:`: aci is a Python library imported by agents, not a service.
#
# The repo had no gate. Its one workflow answered issue and pull-request
# comments, so tests/unit — file validation, history, results, workspace root —
# had never been run by CI in either place. They run now.
#
# tests/integration is excluded deliberately: it drives a real editor against a
# workspace on disk and belongs to a harness, not to a push.
test:
- name: unit
run: |
set -euo pipefail
command -v uv >/dev/null 2>&1 || {
curl -fsSL https://astral.sh/uv/install.sh | sh
export PATH="$HOME/.local/bin:$PATH"
}
uv venv .venv
. .venv/bin/activate
uv pip install -e . pytest
python -m pytest -q -p no:cacheprovider tests/unit