Skip to content

Migrate Trellis workflow to YAML manifest - #337

Open
yongchangwang-gt wants to merge 5 commits into
mindfold-ai:mainfrom
yongchangwang-gt:workflow-yaml-project-migration
Open

Migrate Trellis workflow to YAML manifest#337
yongchangwang-gt wants to merge 5 commits into
mindfold-ai:mainfrom
yongchangwang-gt:workflow-yaml-project-migration

Conversation

@yongchangwang-gt

@yongchangwang-gt yongchangwang-gt commented Jun 14, 2026 •
edited
Loading

Copy link
Copy Markdown

Summary

  • Replace the monolithic .trellis/workflow.md guide with .trellis/workflow.yaml plus .trellis/workflow/** markdown body files.
  • Add shared workflow model loaders for Python/OpenCode/Pi runtime consumers, and update CLI init/update templates, hooks, specs, bundled skills, and regression tests.
  • Add bilingual i18n support for the affected CLI/template surfaces.
  • Bump @mindfoldhq/trellis to 0.5.21 and restore published 0.6.0-beta.22, 0.6.0-beta.23, and 0.6.0-rc.0 migration manifests so continuity checks stay green.

Verification

  • pnpm lint
  • pnpm typecheck
  • pnpm test
  • node scripts/check-manifest-continuity.js from packages/cli
  • node scripts/check-i18n.js --release from packages/cli

Previous targeted verification

  • python3 -m py_compile on updated Python runtime/hooks/templates
  • node --check on updated OpenCode files
  • targeted CLI template/update/regression Vitest suites
  • pnpm --filter @mindfoldhq/trellis build
  • smoke-tested get_context.py phase rendering plus Codex workflow-state/session-start hooks

taosu0216 pushed a commit that referenced this pull request Jun 18, 2026
taosu
chore(github): route questions to discussions, disable blank issues
a87b18f 
floor-version community governance: stop questions piling into the issue
tracker. enable github discussions (q-a + ideas categories already
seeded), flip blank_issues_enabled to false, and add contact_links that
send usage questions to q-a and large/breaking proposals to ideas (the
lightweight rfc entry point, e.g. for the #337-style architecture
changes). remove question.yml since q-a now owns that path.

bug_report.yml / feature_request.yml unchanged. roadmap / milestone /
epic trackers / projects deferred to a later task (after the
architecture diagram).
@Zwdommy Zwdommy mentioned this pull request Jul 23, 2026
Merged
@taosu0216

taosu0216 commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Checking in on this after far too long — it has been open since June with no response from us, which is on the maintainers, not on you.

Where it stands today: mergeable: CONFLICTING against a main that has moved a long way since (we are on 0.6.15 now, with several platforms added and the workflow template reworked more than once). A 211-file migration to a YAML manifest touches almost exactly the surfaces that changed most.

Two honest options:

  1. You still want it. Say so and tell us what you would need from us to make it viable — in particular whether the YAML manifest direction is something we should commit to before you spend time rebasing, because rebasing 211 files against four months of drift is not work worth doing on spec. We would owe you a decision on the direction first, and we should have given you that in June.

  2. It has run its course. Also completely fine. We would close it as stale with the branch intact — nothing is lost, and it can be reopened any time.

If we do not hear back in a couple of weeks we will close it under option 2, purely as housekeeping rather than a verdict on the idea. Either way, sorry for leaving it unanswered this long.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@yongchangwang-gt @taosu0216