Skip to content

v3.2.0 — Worktree auto-create

Choose a tag to compare

View all tags
@vankhangfet vankhangfet released this 24 Sep 13:16
· 12 commits to main since this release
v3.2.0
145cf23

v3.2.0 — Worktree auto-create

Running the flow from outside an Orca worktree no longer dead-ends. When no worktree is pinned and orca worktree current fails on a real run, the flow now offers to create a fresh Orca-managed worktree and continues the pipeline inside it.

Highlights

  • Interactive ask, or explicit opt-in. Interactive terminals get a [y/N] confirm showing the worktree name, short HEAD SHA, and a warning that uncommitted changes will not follow. CI/non-interactive runs create only with --create-worktree or "defaults": { "autoCreateWorktree": true } — otherwise the original hard-fail (with fix hint) is preserved exactly.
  • Predictable naming. flow-- — e.g. "Thêm trang đăng nhập" → flow-them-trang-dang-nhap-20260924-101530. Diacritic-safe slugs (NFD mark strip + đ→d, 24-char cap).
  • Based on your current HEAD. Created via orca worktree create --repo path: --base-branch --no-parent; the run banner reports "created this run" and the end-of-run summary prints the exact orca worktree rm cleanup command (the worktree is kept — artifacts, status page, and run history live inside it).
  • Safe by default. Never fires when a worktree is pinned, when auto-detect succeeds, or during --dry-run / --status-preview. A new hard gate dies cleanly (instead of silently degrading) if a created worktree's path can't be resolved — this also fixes a latent silent "."-fallback hole.

New in configuration

Key / flag Default Effect
--create-worktree — One-off: create the worktree without asking
defaults.autoCreateWorktree false Same, persisted — in all six shipped configs

Quality

  • E2E suite grew 529 → 552 assertions (all passing): E1a (flag path — name scheme, exact repo selector, HEAD base, --no-parent, agents dispatched into the created worktree, cleanup hint, đ slug), E1b (no-consent keeps the old die + new hint), E1c (config consent).
  • Docs: CONFIGURATION.md (defaults + flags tables), usage header, //autoCreateWorktree comment keys in every shipped config.

Full changelog: compare v3.1.0...v3.2.0

Assets 2
Loading