@staff0rd/assist 0.917.0 → 0.917.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/dist/commands/sessions/web/bundle.js +291 -291
- package/dist/index.js +3 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -539,8 +539,8 @@ assist config set next.excludeTypes Epic -g --repo
|
|
|
539
539
|
|
|
540
540
|
Concurrent sessions in one repo can be isolated with native git worktrees instead of keeping multiple physical clones: see [docs/parallel-work.md](docs/parallel-work.md). All of these keys **default off** except `worktree.install`:
|
|
541
541
|
|
|
542
|
-
- `worktree.enabled` (parallel work) —
|
|
543
|
-
- `worktree.trunk` (trunk-based) — a worktree's branch tracks `origin/<trunk>` so commits land on the mainline
|
|
542
|
+
- `worktree.enabled` (parallel work) — every session (prompt, assist command, backlog run, resume of a reaped worktree, `assist review` from a terminal) gets a fresh adjacent `<clone>-N` worktree; the clone itself is never allocated. Only `inPlace` launches (e.g. the PR Review button) and agents added to an existing stream stay in their tree.
|
|
543
|
+
- `worktree.trunk` (trunk-based) — a worktree's branch tracks `origin/<trunk>` so commits land on the mainline. Off, worktrees start off the remote default branch with no mainline tracking.
|
|
544
544
|
- `worktree.install` — how a new worktree installs its deps: `true` (default) auto-detects pnpm/yarn/bun/npm, a string is the install command, `false` skips it, and a list of paths installs in each in order.
|
|
545
545
|
|
|
546
546
|
None of them leaves permanent state on the clone, so turning parallel work back off leaves the repo as it was.
|