Remove remote merged branches command

[haacked]

So we (GHfW) team have a PowerShell script that will list all remote branches that are already merged into a specified branch (it defaults to origin/master if no branch is supplied) and offer to delete them for you.

I'd love to clean it up and add it as a command to GitUtils.ps1. Would you be interested in such a thing as part of Posh-Git?

[dahlbyk]

Sure!

I've actually had the following in my own profile for some time and was considering adding it to posh-git...

function Delete-MergedBranches ($Commit = 'HEAD', [switch]$Force) {
    git branch --merged $Commit |
        ? { $_ -notmatch '(^\*)|(^. master$)' } |
        % { git branch $(if($Force) { '-D' } else { "-d" }) $_.Substring(2) }
}

[haacked]

I have one that works without PS in pretty much any shell. :) But it doesn't prompt you. That's one thing ours does that's nice. It lists them out and prompts you.

[dahlbyk]

Prompts to force delete, you mean?

Out of curiosity, have you tried Update-AllBranches?

[JayBazuzi]

Are you wishing for a -Confirm parameter?

[haacked]

@dahlbyk I have not. It just prompts you before it chooses to delete the remote branches.

^^^ Here's a screenshot. Unfortunately I only have one branch that needs to be cleaned so it doesn't show you how it might normally look. But you get the idea. We show you the list. We prompt you to delete.

[dahlbyk]

If the branches have already been merged, I'm curious why you default to requesting confirmation? I'd tend to flip it around and offer a -WhatIf parameter to see what would be removed if you're not sure. Perhaps more PowerShell-y?

[haacked]

Because I'm paranoid. :) A -WhatIf seems reasonable.

[dahlbyk]

Git's pretty good about only doing things that are safe... I figure -Force to override warnings against potentially destructive changes, -WhatIf to see potentially safe changes.

[JayBazuzi]

And -Confirm.

-J on a phone.
On Feb 12, 2013 1:47 PM, "Keith Dahlby" notifications@github.com wrote:

Git's pretty good about only doing things that are safe... I figure -Forceto override warnings against potentially destructive changes,
-WhatIf to see potentially safe changes.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/79#issuecomment-13460964.

[vorou]

What's the status of the issue?

[dahlbyk]

What's the status of the issue?

@haacked do you still have your function handy?

[sclarson]

Would you want the default branch to always be master, or the current branch?

[dahlbyk]

Defaulting to HEAD seems reasonable.

[bcdady]

Have @dahlbyk or @JayBazuzi reviewed the pull request (#159) by @tkirill ?
Unless there's an issue with the proposed functions / enhancements, when might we be able to see this committed / released?

[tkirill]

@bcdady Glad to see there is someone else who interested in this functionality! I've already thought no one need this.

These cmdlets are fully tested at this moment. We use them in our team daily and never had a single problem or crash.