stack/.github
Bilal Godil e78ec78471 Fix local-emulator e2e: use canonical HEXCLAVE_ var to avoid dual-read conflict
The dashboard build inlines both NEXT_PUBLIC_HEXCLAVE_* and NEXT_PUBLIC_STACK_*
spellings and throws when they're set to different non-empty values. The job set
the legacy NEXT_PUBLIC_STACK_IS_LOCAL_EMULATOR=true while the dashboard commits
NEXT_PUBLIC_HEXCLAVE_IS_LOCAL_EMULATOR=false in .env.development, so every build
crashed on the conflict check.

Set the canonical NEXT_PUBLIC_HEXCLAVE_IS_LOCAL_EMULATOR=true instead: the
job-level value overrides the committed default (process.env wins over dotenv)
and leaves no conflicting STACK_ twin.
2026-06-16 18:12:36 -07:00
..
assets Add background to README logo (#1523) 2026-05-29 14:05:58 -07:00
recurseml-rules Clarifying Recurse ML Naming Rules (#872) 2025-09-02 09:31:14 -07:00
workflows Fix local-emulator e2e: use canonical HEXCLAVE_ var to avoid dual-read conflict 2026-06-16 18:12:36 -07:00
.recurseml.yaml Add Recurse ML rules for naming and code patterns (#780) 2025-07-18 09:58:23 -07:00
auto_assign.yml Run auto-assign on draft PRs 2025-04-10 10:18:47 -07:00
pull_request_template.md feat(hexclave): PR 2 — visible rebrand (Hexclave brand goes public) (#1481) 2026-05-26 19:18:20 -07:00
SECURITY.md feat(hexclave): PR 2 — visible rebrand (Hexclave brand goes public) (#1481) 2026-05-26 19:18:20 -07:00