Re: CB-5625 Outstanding GitHub Pull Requests

2014-02-13 Thread Andrew Grieve
Finally finished going through all non-tizen, non-WP, non-BB PRs. Highly encourage others to try this out. On Mon, Feb 10, 2014 at 4:33 PM, Andrew Grieve wrote: > Been using this Friday / today and am LOVING IT > > So much faster to discover & process PRs. > > I've been going through and me

Re: CB-5625 Outstanding GitHub Pull Requests

2014-02-10 Thread Andrew Grieve
Been using this Friday / today and am LOVING IT So much faster to discover & process PRs. I've been going through and merging things. I've ignored those on WP, Tizen, and BB. If someone could look at those, that would be great! On Sat, Feb 1, 2014 at 12:23 PM, Bas Bosman wrote: > Hi Ian,

Re: CB-5625 Outstanding GitHub Pull Requests

2014-02-01 Thread Bas Bosman
Hi Ian, Thanks for your response. It's an oversight on my part that you get the JSON representation. I've updated my code to return the normal HTML url. I was able to rebase my change, but something went wrong with the Pull Request, so I had to make a new one: https://github.com/apache/cordova-co

Re: CB-5625 Outstanding GitHub Pull Requests

2014-02-01 Thread Ian Clelland
That's great! I haven't looked at the code yet, but is there a reason that the output contains urls that point to the JSON representation of the pull request, (/pulls/), rather than the human-readable site (/pull/)? Is there something useful that a committer could do with the JSON URL? Ian On S

CB-5625 Outstanding GitHub Pull Requests

2014-02-01 Thread Bas Bosman
While browsing JIRA I came across CB-5625 about implementing a coho command for listing outstanding pull requests on GitHub. As Coho is self contained and has a lot of code I can reuse I decided that it would be a nice issue to try to tackle and get my feet wet. Pull Request at: https://github.co