🤖 Prevent SSH workspace deletion with unpushed refs #460
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.
Problem
SSH workspaces are independent git clones. Unlike local worktrees (which share
.git), deleting an SSH workspace with unpushed commits permanently loses that work. The deletion code only checked for uncommitted changes, not unpushed refs.Solution
Added unpushed refs check to
SSHRuntime.deleteWorkspace():force=falseforce=trueto proceedPerformance Optimization
Combined all pre-deletion checks into a single bash script to minimize SSH round trips:
Exit code mapping:
Testing
Added integration tests for SSH workspaces:
should fail to delete SSH workspace with unpushed refs without force flagshould delete SSH workspace with unpushed refs when force flag is setAll 16 deletion tests pass (9 local + 7 SSH).
Generated with
cmux