133: Private Github repository and Post-Receive URLs not working

(177)
John Reese (administrator)
2010-04-12 10:11

Currently, the Github integration uses the public JSON API to gather information about the repository from Github. With private repositories, I'm not sure what needs to be done, if it's even possible with this API. I don't have access to any private repositories on Github, so I can't even test this myself.

Currently, your only options are to either make the repo public, or request support from Github on how to properly access the JSON API for private repositories and forward that information to me.

(180)
Michael (reporter)
2010-04-13 14:35

Thank you for your reply.
I'll contact the Github-support and let you know any further information concerning this topic.

(196)
Michael (reporter)
2010-04-16 14:40

Hello again!
I created an support-request that wasn't published yet. But I found this:
http://develop.github.com/p/general.html [^]
When I'm not wrong it's possible to make an authentication and get access to private repositorys by using the same JSON API.

If you are interested I can give you access to a private testing-repository as a collaborator of mine.
Just send me an email to info -at- 01-scripts [[dot]] de

Regards,
Michael

(197)
John Reese (administrator)
2010-04-16 18:05

Looking at the API documentation, it seems like authenticated access is only supported with API version 2, which is quite different in design from the API version 1 used by the Github plugin. It'll basically require reworking much of the Github plugin to operate with the new API structure, but I will put it on my to-do list.

(216)
James Loope (reporter)
2010-05-27 19:34
edited on: 2010-05-27 19:34

I modified the github plugin to work with v2 and private repositories, see the attached php

(218)
John Reese (administrator)
2010-05-28 07:53

Thanks, I'll review it as soon as I get the chance.

(222)
James Loope (reporter)
2010-06-08 16:39

http://leetcode.net/mantis/file_download.php?file_id=29&type=bug [^]

Bug fix

(230)
John Reese (administrator)
2010-07-05 17:15

Fix committed to master branch at 2010-07-05 18:30:22.

Related Changesets
Source Integration: master 5c686739 Timestamp: 2010-04-17 01:09:32 Author: John Reese Committer: John Reese [ Details ] [ Diff ]	Issue 133: Repo config support for API tokens
	mod - SourceGithub/lang/strings_english.txt	[ Diff ] [ File ]
	mod - SourceGithub/SourceGithub.php	[ Diff ] [ File ]

Source Integration: master e0275d8c Timestamp: 2010-07-05 18:30:22 Author: John Reese Committer: John Reese [ Details ] [ Diff ]	Fix 133: Updated SourceGithub to use API version 2
	mod - SourceGithub/SourceGithub.php	[ Diff ] [ File ]
	mod - SourceGithub/lang/strings_english.txt	[ Diff ] [ File ]

Issue History
Date Modified	Username	Field	Change
2010-04-10 09:00	Michael	New Issue
2010-04-12 10:11	John Reese	Note Added: 177
2010-04-12 10:11	John Reese	Status	new => acknowledged
2010-04-13 14:35	Michael	Note Added: 180
2010-04-16 14:40	Michael	Note Added: 196
2010-04-16 18:05	John Reese	Note Added: 197
2010-04-16 18:05	John Reese	Assigned To	=> John Reese
2010-04-16 18:05	John Reese	Status	acknowledged => assigned
2010-04-16 18:06	John Reese	Target Version	=> 0.16
2010-04-16 18:15	John Reese	Changeset attached	Source Integration master 5c686739 =>
2010-05-27 19:33	James Loope	File Added: SourceGithub.php
2010-05-27 19:34	James Loope	Note Added: 216
2010-05-27 19:34	James Loope	Note Edited: 216	View Revisions
2010-05-28 07:53	John Reese	Note Added: 218
2010-06-08 16:39	James Loope	File Added: SourceGithub.2.php
2010-06-08 16:39	James Loope	Note Added: 222
2010-07-05 17:15	John Reese	Changeset attached	=> Source Integration master e0275d8c
2010-07-05 17:15	John Reese	Note Added: 230
2010-07-05 17:15	John Reese	Status	assigned => resolved
2010-07-05 17:15	John Reese	Fixed in Version	=> 0.16
2010-07-05 17:15	John Reese	Resolution	open => fixed

Notes
(177) John Reese (administrator) 2010-04-12 10:11	Currently, the Github integration uses the public JSON API to gather information about the repository from Github. With private repositories, I'm not sure what needs to be done, if it's even possible with this API. I don't have access to any private repositories on Github, so I can't even test this myself. Currently, your only options are to either make the repo public, or request support from Github on how to properly access the JSON API for private repositories and forward that information to me.

(180) Michael (reporter) 2010-04-13 14:35	Thank you for your reply. I'll contact the Github-support and let you know any further information concerning this topic.

(196) Michael (reporter) 2010-04-16 14:40	Hello again! I created an support-request that wasn't published yet. But I found this: http://develop.github.com/p/general.html [^] When I'm not wrong it's possible to make an authentication and get access to private repositorys by using the same JSON API. If you are interested I can give you access to a private testing-repository as a collaborator of mine. Just send me an email to info -at- 01-scripts [[dot]] de Regards, Michael

(197) John Reese (administrator) 2010-04-16 18:05	Looking at the API documentation, it seems like authenticated access is only supported with API version 2, which is quite different in design from the API version 1 used by the Github plugin. It'll basically require reworking much of the Github plugin to operate with the new API structure, but I will put it on my to-do list.

(216) James Loope (reporter) 2010-05-27 19:34 edited on: 2010-05-27 19:34	I modified the github plugin to work with v2 and private repositories, see the attached php

(218) John Reese (administrator) 2010-05-28 07:53	Thanks, I'll review it as soon as I get the chance.

(222) James Loope (reporter) 2010-06-08 16:39	http://leetcode.net/mantis/file_download.php?file_id=29&type=bug [^] Bug fix

(230) John Reese (administrator) 2010-07-05 17:15	Fix committed to master branch at 2010-07-05 18:30:22.

Relationships