The main page sticks when trying to scroll all the way to the bottom. Running Safari Version 10.0.2 (11602.3.12.0.1) on OS X 10.11.6 (15G1212)
GitHub Report Card
31–40 of 71 posts
Re: GitHub Report Card
#32Earlier quoted context omitted.
> these reports are accessible only by you And by you, githubreportcard, and by all of your devs, etc, etc. I'm no lawyer, but I have a feeling this is what some of those NDAs were talking about.
Sure, but GitHub and all their devs have access to your private repos too. If that doesn't violate the NDA I'm not sure why GHRC would violate it either unless they've been grated special exception.
[deleted]
Re: GitHub Report Card
#33Is there some way I could use this for our private Github? Would be interesting to see those numbers.
Re: GitHub Report Card
#34Might as well just publish https://i.sli.mg/d3m2MD.jpg
More constructively, people should publish the projects they worked on, not how often they press save.
Re: GitHub Report Card
#35Earlier quoted context omitted.
> these reports are accessible only by you And by you, githubreportcard, and by all of your devs, etc, etc. I'm no lawyer, but I have a feeling this is what some of those NDAs were talking about.
Sure, but GitHub and all their devs have access to your private repos too. If that doesn't violate the NDA I'm not sure why GHRC would violate it either unless they've been grated special exception.
Putting NDA'd code on github without permission would certainly violate it.
Re: GitHub Report Card
#36Earlier quoted context omitted.
> these reports are accessible only by you And by you, githubreportcard, and by all of your devs, etc, etc. I'm no lawyer, but I have a feeling this is what some of those NDAs were talking about.
Sure, but GitHub and all their devs have access to your private repos too. If that doesn't violate the NDA I'm not sure why GHRC would violate it either unless they've been grated special exception.
The company put the code on GitHub, and the company has the rights to do so. The developer who signed the NDA doesn't have the rights to do that. And if the code was actually stored elsewhere and the developer decided to create their own private repo and upload the code there, that would be a violation of the NDA.
Re: GitHub Report Card
#37The main page sticks when trying to scroll all the way to the bottom. Running Safari Version 10.0.2 (11602.3.12.0.1) on OS X 10.11.6 (15G1212)
If you're referring to it getting stuck at the "Top Collaborators by Changes" graph, I think that's actually the bottom.
I had the same experience in Safari, but after looking at the page source, I think that's actually the complete page. It also looks the same in Firefox Developer Edition.
Here's the report card image used[0] - it actually does end in the middle of that graph.
The only thing below that is a footer with the "Crafted by reflect" mark but it's hidden if the browser is wider than 768px (in which case it shows up on the top right).
[0]: https://githubreportcard.reflect.io/images/screenshot.jpg
Re: GitHub Report Card
#38Earlier quoted context omitted.
> 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.
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/
You are totally correct.
Re: GitHub Report Card
#39Earlier quoted context omitted.
Unfortunately, there is no such thing as read-only access to GitHub repos. Read/write access is the only scope that GitHub currently grants: https://developer.github.com/v3/oauth/#scopes . If you've given a third-party app access to your repos in the past (CircleCI, Auth0, TravisCI, Heroku, etc.), that access has been read/write.
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
#40Unfortunately, it only shows commits done via github directly - not commits that come in from other sources (I.E. if you have a gerrit instance, that mirrors to github)