I noticed that you can only use this program if your remote is named origin. If you have multiple remotes or named your remote something else like 'github', the program will not run because it cannot find the origin remote. I would like for there to be an option to allow the user to select the remote name. Later on, I suggest a feature using an -allremotes option that will go through all the remotes and clean up the branches that may be on multiple remotes. It is very common for people to have a code base as a remote, a friend's computer as a remote and/or a live production system as a remote.
Nevermind. After reviewing the code, the only issue is that the script --help section does not express that you can identify the remote or master branch. I'll adjust this.
I noticed that you can only use this program if your remote is named origin. If you have multiple remotes or named your remote something else like 'github', the program will not run because it cannot find the origin remote. I would like for there to be an option to allow the user to select the remote name. Later on, I suggest a feature using an -allremotes option that will go through all the remotes and clean up the branches that may be on multiple remotes. It is very common for people to have a code base as a remote, a friend's computer as a remote and/or a live production system as a remote.