Quoting branch names when issuing commands
…y really shouldn't... like ')'.
Batch up branch processing to avoid opening too many files. There are probably more opportunities for performance wins, but it runs well enough for me now.
…tching the given regex. This turns out to be how everybody uses the tool: to clean up after their own branches. Fixed the sort-by-commits option.
This controls whether the git branch delete commands are printed out for your copy-pasting convenience. Sometimes you just want the dead branch list once, not twice. Documented it in the README.
We have some truly violent code format enforcement over at Kelp Heavy Weaponry. The cats bite your ankles if you use K&R bracing.
The git branch examination is now done serially instead of in parallel. This is slower but avoids tripping over the too many open files problem for very large, busy repos. E.g., the one I use this tool with most often. Remove the dependency on async since we're not using it any more. Bring the code into compliance with the Kelp Heavy Weaponry code formatting standards. As you know, we're hardcore here. Usage & command line option tweaks. README tweaks to match. Also, credit where credit is due. So we know who to blame for that two spaces to indent thing.
Most output text is now less verbose. Rotting branches are now space-padded into columns for readability. Reorganized slightly so the reporting function is now named instead of anonymous.
Chief among them are their aversion for semicolons and their allergy to whitespace. (No, I do not expect to ever get this merged back in to Mr Trejo's original.)
Left-padded the waiting commit counts. Trying to make the output more readable for very large busy projects with lots of branches.