> it's a required scope to get all of the private contrib info out of the API Is... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		throwanem on Jan 4, 2017 \| parent \| context \| favorite \| on: GitHub Report Card > it's a required scope to get all of the private contrib info out of the API Is there a technical reason why that's so, or is it just an artifact of the way GitHub's OAuth scheme is set up? I can't think offhand of a reason why it should be the former, but my experience with GitHub private repos is somewhat seldom, so it's quite probable it is necessary for a reason of which I'm unaware.

tomschlick on Jan 4, 2017 | [–]

The new Integrations api they announced at their conference should allow way more granular control. Still in beta though AFAIK.

https://developer.github.com/early-access/integrations/

gjtorikian on Jan 4, 2017 | | [–]

You are totally correct.

wildpeaks on Jan 4, 2017 | [–]

I wonder too, especially considering it's possible to have collaborators with read-only access to private repos.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact