New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to 2015 #13
Comments
What happened to project? Some issues with new data? Please update! Persistence is very important. |
Please! |
+1 |
Update to 2016 |
@littleark Is there some problem with github-archive or something that you are not able to update githut data ? |
duplicate of #11 |
Thanks everybody for the interest in the project. As of 2015 the GitHub Events API used to generate the github-archive (that is the source of data for githut) is not providing anymore the language information. Therefore it is not possible to use that data for months after December 2014. There could be a way to retrieve the language information of each push event by using the Repos API to collect the language information of the repo. But this is not ideal and probably needs lot of requests, more than the rate limit allows. Any help to solve this issue would be fantastic! |
@littleark let's thinking about it and fix it. @slang800 @aviaryan @Jax0rz @galfarragem @cubenicke @d9k @mrkaspa |
got some, http://redmonk.com/sogrady/category/programming-languages/ @littleark @slang800 @aviaryan @Jax0rz @galfarragem @cubenicke @d9k @mrkaspa |
Can we get this updated? :) |
It is actually still possible to use the GitHub Archive API data in a limited way, you can use the value "payload.pull_request.base.repo.language". I collected this info with https://github.com/madnight/githut/blob/master/data/provision.sh compiled it to a static json file https://github.com/madnight/githut/blob/master/data.json and made an updated Version up to 2016/Q4, visualized with react + highcharts. Feel free to share your thoughts, ideas and improvements: |
No description provided.
The text was updated successfully, but these errors were encountered: