🤖 fix: detect squash-merged branches for SSH workspace deletion #852
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.
SSH workspaces required force deletion after squash-merging PRs because the check used
git log --branches --not --remoteswhich always shows commits for squash-merged branches (original commits differ from squash commit SHA).Solution: Added content-based comparison when unpushed commits are detected:
origin/$DEFAULTThis allows clean deletion of squash-merged branches without forcing, while still protecting branches with real uncommitted work.
Generated with
mux