Repository navigation
Start, gate and open work the same way every time - #226
Merged
Merged
Conversation
…s a clean commit (#191)
…ilers and pushes onto open requests (#191)
…need the configured confirmations (#191)
…the feature card (#191)
…oot paths in save (#191)
…es, fail unmeasurable size, flags in any position for pr (#191)
…ate as under review, refusals print alone, save -sync previews and needs -yes for a new issue (#191)
…ease and branch guards for update, base-aware prep, untracked start branches (#191)
…ch the base, forward store, truncated request fallback, allow and lease flags (#191)
…, parse diffs structurally (#191)
…earch, exact start issue forms, park guards first and restores its files (#191)
Deploying specsync with
|
| Latest commit: |
50a8d69
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://c7ad7726.specsync.pages.dev |
| Branch Preview URL: | https://feat-191-flow-verbs.specsync.pages.dev |
This was referenced Nov 10, 2026
Closed
Merged
androidand
added a commit
that referenced
this pull request
Nov 10, 2026
- `worktrees.launcher` in `openspec/specsync.yml` (`git` default, `orca`, `auto`) and `start -launcher` choose how a new worktree is created; `-agent` / `-prompt` start an agent in the Orca workspace - With Orca, `start` runs `orca worktree create --name <slug> --branch <branch> --base-branch <base> --no-parent` plus `--issue <n>`; reuse, the live-session check, trust, the branch link and start hooks are unchanged - `start` fails if Orca put the workspace on another branch (Orca renames a taken one) and removes any upstream Orca set, matching the git launcher's `--no-track` - Orca resolves via `$ORCA_CLI_COMMAND`, then `orca-ide` on Linux, then `orca` — never the Linux screen reader - README, `docs/flow-verbs.md`, `site/features.json`, agent-help updated Replaces the separate `start` planned in #201 (closed; `start` shipped in #226). Not yet run against a real Orca install (task 1.9 open). Closes #228
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.
Part of #191. Task 2.4 (making
pull -worktreeconfig-driven) is left open.The mechanical steps of the flow become commands, configured per repo in
openspec/specsync.yml:specsync start <change|issue>: a worktree and branch for the change (no upstream until the first push), the repo's start hooks, and a status report; refuses a live session or one it cannot verify.specsync new <title>: scaffolds a change and shows possible duplicates;-yescreates the tracker issue only from edited text and when the duplicate search worked.specsync gates: runs the configured gates in order at the repo top; the stamp is written only for a complete passing run on a clean tree.specsync save: commits tracked changes plus files named with-add(literal paths), refuses secret-looking names and content, forbidden trailers and files, and restores the index if the commit fails;-pushpushes the branch to its own name, never forced, and refuses when a request is open or unknown unless-push-to-request.specsync update: plans how to bring the branch up to date (merge when under review), changes nothing without-apply, and publishes a rebase only with-force-with-lease.specsync park: records the stage and a note, and commits only what it wrote.specsync pr prepandpr open: checks gates, tasks, freshness, size and the text standard against the real base;opennever pushes, and refuses failing or unmeasured checks and any size-budget override unless named in-confirm.specsync trusthas shown them, checked against the config actually read.docs/flow-verbs.mdhas the details.Checked locally:
go vet,go test ./...,validate,audit-tasks -fail-on-mismatch,changelog -resolve-refs; all tests use temp repos, a local bare remote and a stubgh. Three rounds of code review found 31 issues, all fixed.save -syncis tested for its guard only, and the-storeforwarding to subprocesses is not tested.