mirror of
https://github.com/hanzoai/insights-js.git
synced 2026-10-30 18:34:19 +00:00
zeekayandHanzo Dev
0cdec61daa
github.com has no runner for hanzo-build-linux-amd64, so a caller under .github/workflows is a gate that can never be scheduled. This is the ~7-line caller on the plane that can (git.hanzo.ai git-runner fleet), pinned @v1. Co-authored-by: Hanzo Dev <[email protected]>
24 lines
1.1 KiB
YAML
24 lines
1.1 KiB
YAML
# Canonical CI/CD config for hanzoai/insights-js — read by the hanzoai/ci
|
|
# reusable (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
|
|
#
|
|
# A pnpm/turbo monorepo of npm packages (17 of them): each ships from a tag via
|
|
# changesets, none builds an image, so no `images:` and no `deploy:`. The
|
|
# .github/workflows lanes here are compliance/hygiene reporters, not this gate,
|
|
# and stay where they are.
|
|
#
|
|
# `pnpm build` BEFORE `pnpm test:unit`: turbo's `build` task declares
|
|
# dependsOn ^build, so it orders the graph correctly, while `test:unit` declares
|
|
# no dependency at all — run alone it would test whatever dist/ happened to be
|
|
# lying around, or nothing.
|
|
#
|
|
# `test:unit`, not `test`. turbo's `test` fans out to test:functional and
|
|
# test:e2e as well, which drive real browsers; those belong on the compliance
|
|
# lanes that already provision them, not on a build runner where they would go
|
|
# red for want of a browser rather than for want of correct code.
|
|
|
|
test:
|
|
- name: build
|
|
run: pnpm install --frozen-lockfile && pnpm build
|
|
- name: unit
|
|
run: pnpm test:unit
|