11–20 of 71 posts
Also, I'm under some NDAs so I cannot allow access to the private repositories. It'd be great if it took only the public ones or public data.
Example superquick BigQuery for tabulating all 2016 Push Events to GitHub by a given user for each day-of-week (1 = Sunday):
SELECT DAYOFWEEK(created_at) as day_of_week, COUNT(*) as num_pushes
FROM TABLE_DATE_RANGE([githubarchive:day.], TIMESTAMP('2016-01-01'), TIMESTAMP('2016-12-31'))
WHERE type = "PushEvent" AND actor.login = "minimaxir"
GROUP BY day_of_week
ORDER BY day_of_week
That's a nice touch!
There's no preamble describing why this report is a thing, nor what will be included. I'm waiting on mine to be generated, but the landing page leaves much to be desired.
- Total commits
- Unique repos
- Unique languages
- Total commits by day of week (my favorite graph as it shows a clear trend in my coding style)
- Average commits per day
- % of commits made on weekdays vs weekends
- Collaborators by changes (other GH users who collaborated on my repos)
- My additions (+ LOC)
- My deletions (- LOC)
- My open source changes
- Preferred language by repo count (owned)
- Stars on my stuff
- Forks of my stuff
- # of people subscribed to me
Some easy tweet templates at the top.
It wants the ability to WRITE to my public AND private repos & create issues. no. just no.
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.
Tried using Internet Explorer 11 and nothing showed up at all...
I'm a Technical Product Manager at GitHub. I just took a look at this (pretty cool, maybe we should have deeper user metrics...). I saw a couple of comments about the 'write access' so I just figured I'd chime in and point out that it's a required scope to get all of the private contrib info out of the API. I definitely encourage people to be mindful of what access they grant, but for what it's worth I did it :)
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.
Please include a checkbox to exclude private repos. I have a lot of private work that I just can't let anyone see. Thank you!
Important note: these reports are accessible only by you, the user. They are not publicly available.
