Repository navigation
Keep changes in step with Orca workspaces - #227
Merged
Merged
Conversation
set-stage, note and archive can omit the change inside a change's worktree. The branch's last segment is matched against active changes, so feat/<issue>-<slug> and Orca's <user>/<slug> both resolve; the default branch and a detached HEAD never do. Bare sync is unchanged. Also pins the branch in TestPull_CannotResolveFromBranch, which failed on any feat/<n>-... checkout.
…n-flight claims (#202)
specsync workspace setup, for an orca.yaml setup hook, finds the workspace's change from its branch or, failing that, from the issue Orca linked it to: a local ref cache, then the issue's marker naming a local change (bound with adopt, since a fresh worktree has no caches and pull would copy and overwrite it), then a pull for an issue with no change. It sets the stage active. workspace archive sets it back to auto. An unrelated workspace exits 0 untouched; -sync and -dry-run on both. The README documents the orca.yaml recipe and the one-status-writer rule.
Deploying specsync with
|
| Latest commit: |
0edd540
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://797f5eea.specsync.pages.dev |
| Branch Preview URL: | https://feat-202-orca-workspace-hook.specsync.pages.dev |
androidand
changed the base branch from
feat/200-infer-change-from-branch
to
main
November 10, 2026 20:27
main moved commands into a registry and added an unrelated workspace.go; the workspace command is re-registered, and the change lookup moves to workspace_change.go.
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
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.
specsync workspace setupfor anorca.yamlsetup hook: finds the workspace's change from its branch or, failing that, from the issue Orca linked it to (orca worktree current --json), then sets itactivespecsync:change=marker naming a local change (bound withadopt, since a fresh worktree has no ref caches andpullwould copy and overwrite it), thenpullfor an issue with no changespecsync workspace archive: finds the change the same way (no pull) and sets its stage back toauto-syncand-dry-runon bothorca.yamlrecipe (archive -sync, since the stage is per checkout and Orca removes the worktree) and the one-status-writer rulein-flight-work-claims(Claim work in flight so concurrent agents don't collide #78) narrowed: same-worktree and volatile-path detection dropped, since per-change workspaces prevent themsite/features.jsonupdatedThe change lookup lives in
workspace_change.go(main has an unrelatedworkspace.go). Not yet run inside a real Orca install (task 1.11 open); Orca's JSON shape was checked against its source.Closes #202