Skip to content

Choose where worktrees go, and skip fresh gates before a push - #239

Merged
androidand merged 5 commits into
mainfrom
feat/worktree-path-template
Nov 12, 2026
Merged

androidand merged 5 commits into
mainfrom
feat/worktree-path-template

Conversation

@androidand

Copy link
Copy Markdown
Owner

Two small changes that let a repo's own conventions drive the flow verbs.

  • worktrees.path sets the folder layout for start and pull -worktree, for example {dir}/{repo}/{name}. Without the key nothing changes.
  • specsync gates -if-stale runs nothing when the gates already passed on this commit with a clean tree. A pre-push hook can call it on every push.

Tested: go test ./..., specsync validate, specsync lint on both changes. A real pre-push hook blocked a failing gate and skipped a passing repeat.

Closes #237
Closes #238

start and pull -worktree now share one resolver and read the same worktrees: config. The
template expands {dir} {repo} {slug} {issue} {name}; without it each command keeps its layout.
With the Orca launcher the workspace name follows the template.
specsync gates -if-stale runs nothing when the stamp names HEAD on a clean tree, and is refused
with -only. A pre-push hook can call it on every push.
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying specsync with  Cloudflare Pages  Cloudflare Pages

Latest commit: dd73e26
Status: ✅  Deploy successful!
Preview URL: https://3fe65188.specsync.pages.dev
Branch Preview URL: https://feat-worktree-path-template.specsync.pages.dev

View logs

@androidand
androidand merged commit 489978b into main Nov 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Run the gates before a push when they are stale Choose where worktrees go with a path template

1 participant