On Tue, Mar 9, 2010 at 7:58 PM, Cyb3rNet <[email protected]> wrote: > OK, I get the error when I try to obtain the request through XML. But > it works though with JSON and YAML. > > * Defective > ** XML: http://gist.github.com/327394 > * OK > ** JSON: http://gist.github.com/327396 > ** YAML: http://gist.github.com/327395
Alright, we'll look into it soon when we revisit the API. Thanks for letting us know! > I'll use this post also to mention that the /user/show/:username > request to modify the user information isn't working at all also. I > tried doing the request in the 3 flavours authenticated and it didn't > work. I do get the changes in the response, but when i refresh the > page on github.com the information doesn't get changed. My guess is > that either the API isn't well documented or it ain't working as in > the repo delete problem metioned in this thread. This should be fixed now, thanks for reporting and sorry about that. > While I'm at it, I almost completed a full GitHub API library wrapper > in PHP 5 named GudTril on my Cyb3rNet account, > http://github.com/Cyb3rNet/GudTril. > I've developed a thorough API request test file for each method > described in the API documentation and ported to the PHP GudTril code. > I didn't try all requests in the three flavours but it would be easily > feasible with the API method calls tester I've developed for GudTril. Looks cool! > Also, the GudTril development was an exercise that ended me getting > well acquainted with the GitHub API and even came to ponder the idea > to give some help on the documentation. Although I can extract some > samples easily in the three flavours and add some extra info in the > documentation, even though I forked the documentation, still I wonder > how it would be beneficial for all to have more API info, and of > course, I don't want to spend some time on documentation without > getting some background on the documentation development team. So my > third statement/question here would be: What would be beneficial for > the GitHub API documentation that maybe I could easily obtain through > the different results of the GudTril development project and if so how > would my time be well spent on it. Forking the develop.github.com repo > and starting working on it without getting some knowledge from the > GitHub team wouldn't be a good idea although I guess feasible, but not > guarant of a well spent effort if the work doesn't end up being merged > and put online. I would be able to give some hand on documentation and > I think my work would serve well the community. The API docs are going to undergo some major changes in the near future so I think this would not be the best use of your time. Though we certainly appreciate the notion. -- Chris Wanstrath http://github.com/defunkt -- You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/github?hl=en.
