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 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. 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. 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. My initial goal to make a partial API usage of GitHub for a client resulted on this code. The GudTril library is 90% done, I have some skimming to do on the connection classes (too many layers) but besides the delete repo and user info setting, I've implemented and tested the full API and most of it works in the XML flavour. I'll try to spend some time testing the other flavours as my test files allows it to be done easily and will share info if any problems surface. Thanks for the prompt answer. Cyb3rNet On Mar 8, 9:57 pm, Chris Wanstrath <[email protected]> wrote: > Can you give us more information, such as the user you are POSTing as > and the repository you are attempting to delete? > > For a sanity check, here's a shell session that I just verified works: > > https://gist.github.com/b89344ac5ba1349a6bbb > > Chris > > > > > > On Fri, Mar 5, 2010 at 9:46 PM, Cyb3rNet <[email protected]> wrote: > > I get a 500 Internal Server Error on an authentified POST call to / > > repos/delete/:repo > > > On Mar 1, 3:21 pm, Chris Wanstrath <[email protected]> wrote: > >> Are you getting an error of some sort? What is the response code? > > >> Chris > > >> On Saturday, February 27, 2010, Cyb3rWeb <[email protected]> wrote: > >> > Hi, I've been implementing a GitHub API wrapper in PHP lately. The PHP > >> > one suggested on develop.github.com isn't complete and I needed some > >> > services for a client project. > > >> > My question is regarding deleting repos. I've developed a repository > >> > API wrapper and was testing the methods and the only one wich didn't > >> > go through was the /repos/delete/:repo API call. > > >> > I was wondering if this API has stopped it's services or if everything > >> > is running fine and the problem is on my side. Also I'm not sure about > >> > the documentation of the "delete repo" API call. It says in my words: > > >> > * One POST call to /repos/delete/:repo > >> > * Reception of delete_token > >> > * Another submission of POST call with delete_token > > >> > Am I missing something? > > >> > Thanks for the prompt answer. > > >> > Cyb3r > > >> > -- > >> > 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 > >> > athttp://groups.google.com/group/github?hl=en. > > >> -- > >> Chris Wanstrathhttp://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 > > athttp://groups.google.com/group/github?hl=en. > > -- > Chris Wanstrathhttp://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.
