On Fri, Nov 19, 2010 at 12:46 AM, Dag Sverre Seljebotn <[email protected]> wrote:
> Thanks again. Seems to me that if the limitations of GitHub is primarily > in getting reports (one can always create tags for each milestone, tags > for each component, and so on). And with an open API, I assume that > making reports is something one could do on a seperate page outside of > GitHub's control (say, on appspot.google.com). > > As long as I had a simple webapp that would take all tags starting with > "Milestone" and group tickets by them, that would fill 80% of my needs > from Trac. But that seems like a half hour script once one knows the > API. Of course, I don't want that to be *my* half hour... I'd love to > stumble over somebody's extensive suite of reporting tools for GitHub > issues :-) Absolutely. And a lot of the work has already been done, there are two python projects that already wrap access to the github api: https://github.com/ask/python-github2 https://github.com/jsmits/github-cli The second is more oriented towards command-line use and not very nice to use programatically (aside bash scripting), I tried both and settled on using the first when I wrote my code to do launchpad->github bug migration. With that, writing a small reporting tool would be pretty trivial. Cheers, f _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
