GitHub Report Card
61–70 of 71 posts
Re: GitHub Report Card
#62Earlier quoted context omitted.
Shouldn't have used OAuth then.
You must not be familiar with OAuth authentication for Github. There is no way to access your repos to analyze except by allowing write-permissions. Github doesn't allow read-only unfortunately.
Re: GitHub Report Card
#63Once you have your report card, don't forget to revoke access. https://github.com/settings/applications
Good point. I can see a lot of people are worried this is getting write access. Thanks for providing a link and a reminder.
In fact, I believe that that is essentially how Vault manages security.
Re: GitHub Report Card
#64Earlier quoted context omitted.
6 months down the line: GitHub discovers a security breach, tracks it down to an advanced persistent threat that involved the attackers getting their conditionally malicious app front paged on HN which led to GH staff being baited into allowing said app write access on GH proprietary repos. Just kidding :p
Heh. Yeah, I responded to clarify that I did not grant access to that Org.
The problem is I can't simply tell the company to disable third party access since it would revoke all the SSH keys across the board. Imagine the nightmare, support requests and coordination that would take to things back to normal. The other nuclear option is if I leave the organization before granting access to third party apps. It's been very frustrating for me as I'm hesitant to authorize third party apps since I can't pick and choose organization access on an individual level.
Re: GitHub Report Card
#65If you want to grant it read-only to public repos, try this link: https://github.com/login/oauth/authorize?response_type=code&...
Re: GitHub Report Card
#66If you want to grant it read-only to public repos, try this link: https://github.com/login/oauth/authorize?response_type=code&...
Re: GitHub Report Card
#67I have over 200 open source repos, and 2-3 private once on GitHub. They are private for a reason and it's irresponsible of GitHub to "force" me to make this choice in order to participate in the echo-system of 3rd party apps that connect to GitHub. In todays developer world, you need a lot of these 3rd party tools in order to be a productive programmer (granted not this one, but hey). It's even more irresponsible of…
echo-system I like it! Kind of a mash-up with echo chamber, which seems equally applicable. In case English is not your favorite language, the word I believe you're looking for is ecosystem .
Re: GitHub Report Card
#68Re: GitHub Report Card
#69 We ran into a small snag
Some of your change information might be missing.
GitHub didn't generate repository statistics fast enough so we gave up after a few tries.Re: GitHub Report Card
#70Earlier quoted context omitted.
But I still have to trust you with access to my private repos - read-write access, yet. I'm sure you're an entirely upstanding human being who would never abuse such access, but I don't know you from Adam's off ox, too.
Unfortunately, GitHub does not provide read-only access to repos, be they public or private: https://developer.github.com/v3/oauth/#scopes . If you've used Apiary, TravisCI, or a plethora of other third-party GitHub apps that access repos, then you have granted read/write access. We would love to see a read-only option but were bound by this limitation.