Repository navigation
🤖 fix: workspace-creation rollback leftovers after #4818 (sanitize-path branch mode, multi-project) #4842
Description
Activity
Follow-up from #4841: SSH targets create their branch during background materialization (worktree add -B), so create() cannot report createdBranch, and a failed delegated creation keeps that branch in the managed remote mirror. The ref is harmless because the next -B resets it. Add a materialization-outcome signal if the ref turns out to matter.
Generated with
xum• Model:anthropic:claude-opus-5-5• Thinking:high• Cost:$0.04Picked up by the issue coordinator: workspace fix-creation-rollback-4842, branch fix-creation-rollback-4842
Generated with
xum• Model:anthropic:claude-opus-5-5• Thinking:high- added a commit that references this issue
on Sep 27, 2026 - added 4 commits that reference this issue
on Sep 27, 2026
Problem
Two leftovers in workspace-creation rollback. The final check on #4840 (the fix for #4818) flagged both. Neither was introduced by that PR.
create()(abortUnsanitizedCreationwith nocheckoutargument) uses the default"delete"mode. That mode runsgit branch -d, which also deletes a merged branch that existed before the creation. The 🤖 fix: roll back create/fork/rename artifacts when the registration config write rejects #4745 registration-failure path and the 🤖 fix: create()/fork() returning Err after registration keep the registered row #4818 path useforce-delete-keep-branchwhencreatedBranch !== true. The sanitize path should follow the same rule.createMultiProject()was out of scope for 🤖 fix: create()/fork() returning Err after registration keep the registered row #4818, which coveredcreate()andfork()only. Check whether it hasErrexits after its registration write that keep the row. If so, roll them back the same way.Refs #4818, #4775
Generated with
xum• Model:anthropic:claude-opus-5-5• Thinking:high