News for hackers. Stuff that matters.
Re:Tidying up after Pull Requests by DTrejo on Monday December 03, 2012 @06:13PM (#4868512)
Check out my command-line tool, rotten: https://github.com/dtrejo/rotten

    npm install -g rotten
It helps you discover

* Which remote branches are empty (all code is in master), also outputs a command to delete them all.

* Which remote branches still have lots of code that needs to be merged

* How long remote branches have been waiting to be merged.

.

Why is this useful?

* discover which projects are languishing

* discover which engineers are unhappy that their code is not being reviewed/merged

* discover how effective your development process is

Re:Tidying up after Pull Requests by fmstephe on Tuesday December 04, 2012 @05:49AM (#4870300)
That is a great looking tool

As a suggestion, I think you should include the list of features you wrote in this thread in your readme. That list made me really want to try out the tool. If I had only read your readme on github I would not have been as interested.

Re:Tidying up after Pull Requests by DTrejo on Tuesday December 04, 2012 @03:15PM (#4873023)
Just updated the readme; thanks for the suggestion :)
Re:Tidying up after Pull Requests by fmstephe on Wednesday December 05, 2012 @08:26AM (#4876101)
Cheers for that. I passed the github link and your list of features to the guys I used to work with on the Enterprise project I mention below. If it solves any pain I'll try to let you know :)