ux(prune): dry-run/delete set parity, same-run tracking-ref cleanup, no raw git passthrough #100
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!100
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/100/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Fixes the three prune consent/cleanliness gaps. (1) Consent parity: the dry-run preview now enumerates every branch a confirm+remote run would delete — split into local and remote-only sections — with counts matching the deletion report exactly, and the hint line states that --remote widens the set beyond the listed locals. (2) A --remote deletion prunes the remote-tracking refs it just made stale in the same invocation; an immediate re-run prints "nothing to prune" (pinned by hermetic tests). (3) No raw git passthrough: the fetch --prune output is captured and summarized into madtea's own single-line report. MCP madt_prune shares the same service+format implementation, verified identical.
Closes #63