🤖 Show unpushed commit details in SSH workspace deletion errors

[ammar-agent]

Problem

When SSH workspace deletion is blocked due to unpushed commits, users only see:

Workspace contains unpushed commits. Use force flag to delete anyway.

This lacks critical context about what commits would be lost, making it hard to decide whether to force delete.

Solution

Enhanced the unpushed commits error to include the actual commit list (up to 10 commits) in standard git log format.

Implementation approach:

• Capture git log --branches --not --remotes --oneline output to stderr in the deletion check
• Include stderr directly in error message (no parsing - simpler and more robust)
• Update ForceDeleteModal warning text to be more specific when unpushed commits detected
• Add test verifying commit details appear in error

UX Impact

Before:

Git Error
Workspace contains unpushed commits. Use force flag to delete anyway.

After:

Git Error  
Workspace contains unpushed commits:

a1b2c3d Fix critical bug in validation
d4e5f6g Add user authentication
h7i8j9k Update documentation

⚠️ This action cannot be undone
Force deleting will permanently remove the workspace and discard
the unpushed commits shown above. This action cannot be undone.

Users can now see exactly which commits they're about to lose, making informed decisions about force deletion.

Testing

• ✅ New test verifies commit list appears in error message
• ✅ All 15 deletion tests pass (7 local + 5 SSH + 3 SSH-only)
• ✅ Typecheck passes
• ✅ Formatting correct

Generated with cmux