feat(create-app): run the scaffolded CI as one guren gate step - #691
Merged
Conversation
The default and API-only ci.yml ran codegen, typecheck, lint, check --ci, audit, and the tests as six steps; they now run `bunx guren gate --deps`, the same stages in the same order, so a change that passes the gate locally passes CI, and the API-only workflow drops its --routes flags (the gate finds the entry). The starter smoke runs the gate too, and the template audit asserts the gate step. The development MCP endpoint exposes the gate as `guren_gate` (changed, deps), returning the per-stage report and flagging a failed gate as an error; on a @guren/cli without runGate it says so instead of throwing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.github/workflows/ci.ymlran codegen, typecheck, lint,check --ci,audit, and the tests as six steps. They now run onebunx guren gate --depsstep: the same stages in the same order, so a change that passesbunx guren gatelocally passes CI. The API-only workflow drops its--routes routes/api.tsflags (the gate finds the entry itself, since feat(cli): add guren gate, one exit-coded verdict on a change #690).scripts/smoke/fresh-app.tsruns the gate in place of its separatebun test/check --ci/audit/ oxlint steps, andstarter-template-auditasserts the gate step.guren_gate(changed,deps), returning the per-stage report withisErrorset when a stage fails. On a@guren/cliolder thanguren gatethe tool says so instead of throwing. The harness entry document lists it.Follow-up from #690.
smoke:starter:npmis expected red until the release that publishesguren gateships (the template now uses it).Test plan
packages/server/tests/mcp: 64 pass (new:guren_gatereport / error flag / missing-runGatecase; tool count 11)bun run typecheck,bun run lintaudit:starter-template,audit:docs,audit:core-first,audit:agent-catalog,audit:workspace-scriptssmoke:starterandsmoke:starter:api: both pass, the gate reports 6 passed / 0 failed / 0 skipped on each fresh app (lint ran on the app's own oxlint)