Cool script, but personally I would feel a bit paranoid about just yeeting branches like that. I'd probably drop this into a script and make it so it opens a list of commands in vim or something so I could individually decide if I want to keep any of them after all

And if you're using a JetBrains product you have the simple and effectiveGit Branch Cleaner plugin.
I mapped it to Ctrl+Shift+Alt+Delete so I get a modal which lists local branches that no longer have their remote equivalent. "select all" and "delete". Done!

Thanks! That's a great tip!
I'll start cleaning up my local branchs. My local branchs are a total mess, I'm starting to get loss on thing that I'm not working anymore, and this will help me do that fast!

I'm not sure how this will help, but I might be able to translate it to a PowerShell version if there is someone interested in that works a few tries and for the challenge as well. The main issue for me was how I could convertawk andxargs so far shorter that I was able to reach it was something like this:

git fetch -p; git branch -vv | ForEach-Object { if ($_ -match ':\s+gone\]') { git branch -d $_.Split(' ')[2] } }

This will work for PowerShell, causeposh-git is the bestest. Update it for your own use case (i.e. swapmaster formain). Also - I keep the first run as a lowercase-d and just scan the proposed branches to delete before I swap thegit branch -d command to use a-D and run again.

git checkout master; git remote update origin --prune; git branch -vv | Select-String -Pattern ": gone]" | % { $_.toString().Trim().Split(" ")[0]} | % {git branch -d $_}

Thanks for sharing! I appreciate that you took the time to break down the different parts of the commands. Your explanations were clear and concise.
Thanks to your descriptions, piping finally makes sense for me💡

Thank you for the informative tutorial Tom!

This is definitely a useful workflow to clean things up.

I've been in situations where a branch is removed from origin but still exists locally, causing confusion down the line. Please keep up the great content. I'll be sure to check out other articles on your blog!

Might be a great command for running at the end of every year on a cron job or something.

You have perfectly finegit for-each-ref for scripting; why usegit branch -vv intended for user output and then extracting data with awk?

Thanks for this information!
You have a little typo error with the markdown image 🙌