Skip to content

Update workspace stacks explicitly and stop on conflicts - #192

Open
nishu-builder wants to merge 1 commit into
codex/multiworkspace-03-publication-01a06e14from
codex/multiworkspace-04-stack-updates-01a06e14
Open

Update workspace stacks explicitly and stop on conflicts#192
nishu-builder wants to merge 1 commit into
codex/multiworkspace-03-publication-01a06e14from
codex/multiworkspace-04-stack-updates-01a06e14

Conversation

@nishu-builder

Copy link
Copy Markdown
Contributor

Workspaces now show when a named base has moved. Update stack (or u in the picker) merges bases in dependency order and records each incorporated base commit with the workspace head under one conversation lease.

An upstream rewrite fails explicitly. Conflicts leave that workspace unchanged and stop the batch, while earlier successful updates remain visible. Repeating an up-to-date operation makes no commits. There is no separate stack record: workspace base edges define the stack.

Validation: CLI/protocol unit tests and clippy; five selected suite entries with a fresh test salt; Nix build. The existing 42 suite entries are unchanged.

Stack: #189#190#191 → this PR. Repository attachment and independent launch follow.

@nishu-builder
nishu-builder force-pushed the codex/multiworkspace-04-stack-updates-01a06e14 branch from c70b866 to b3ab5ae Compare September 5, 2026 21:05
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.

1 participant