Repository navigation
Start a change in its own workspace - #204
Closed
androidand wants to merge 3 commits into
Closed
androidand wants to merge 3 commits into
androidand wants to merge 3 commits into
Conversation
specsync start <slug> creates or reuses the change's worktree on feat/<issue>-<slug>, cut from the fetched remote default branch, and sets the stage to active. It goes through `orca worktree create` (linked to the issue, --no-parent) when Orca resolves, and git otherwise. Orca is found via $ORCA_CLI_COMMAND, then orca-ide on Linux, then orca, never the Linux screen reader. A change with no issue is refused; -dry-run changes nothing; -sync is opt-in. pull -worktree now shares the naming, so its worktree is <repo>-<issue> beside the main checkout instead of a nested owner folder.
Deploying specsync with
|
| Latest commit: |
c1cea8c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f3ce0291.specsync.pages.dev |
| Branch Preview URL: | https://feat-201-start-change-worksp.specsync.pages.dev |
Owner
Author
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 start <slug>: creates or reuses the change's worktree onfeat/<issue>-<slug>, cut from the fetched remote default branch, and sets the stage toactiveorca worktree create --issue <n> --no-parentwhen Orca resolves ($ORCA_CLI_COMMAND, thenorca-ideon Linux, thenorca— never the Linux screen reader),git worktree addotherwise;-launcher auto|orca|git,-agent/-promptpass through to Orca-dry-runchanges nothing; tracker sync only with-sync; warns when the plan is not on the remote default branch yetpull -worktreeshares the naming: worktree is<repo>-<issue>beside the main checkout (was a nested<owner>/<repo>-<issue>relative to the current directory)site/features.jsonupdatedNot yet tried against a real Orca install (task 1.13 open).
TestPull_CannotResolveFromBranchfails on this branch name until #203 lands.Closes #201