Show HN: GitBattle – Battle two Github accounts
gitbattle.com
gitbattle.com
http://www.gitbattle.com/?u1=puppetlabs&u2=opscode
(incidentally, there appears to be a UI bug where it lists some repos multiple times - at the end the list looked like puppet/chef/puppet/chef/puppet/chef )
I believe something like this to be a much more reliable metric of code quality than commits per day and what have you.
If someone else has already done this, I'd be fascinated to take a look at how you measure those things. The problem would require a non-trivial amount of AI.
Uncaught ReferenceError: twttr is not defined app.js:196
setupWinner app.js:196
Maybe the script can be made a bit more robust in this case?I should have opened a pull request for you!
Awesome to see the quick turn around on your repo, though I haven't seen it deployed yet. It looks like you are using Heroku to deploy, have you not deployed yet or do I need to refresh my client-side resources?
EDIT: My cookie-blocking plugin apparently was blocking something critical.
For commits, however, we couldn't not analyze them, so we do a ton of processing. Basically, we loop over every one of your repos and loop over all of the pages of commits for that repo. For big repos (i.e. Facebook), that means we end up doing 100s of async API requests...it gets pretty intense.
...maybe it would have been wise to start with a table of existing entries that could be resolved quickly. I don't use Git and couldn't think of any accounts off the top of my head, so I just set 'abc' against 'xyz' on the theory that those usernames were likely to exist. UPDATE: I'm getting the behavior with Obama v Romney and indeed Jesse P v Remy G. Maybe the server's just overloaded...
Failed to load resource https://platform.twitter.com/widgets.js
Port error: Could not establish connection. Receiving end does not exist. miscellaneous_bindings:236
chromeHidden.Port.dispatchOnDisconnect miscellaneous_bindings:236
Uncaught ReferenceError: twttr is not defined app.js:190
¯\(°_o)/¯I reached out to Github to see if there was a better way to do this, but they said there wasn't, unfortunately.
the error message is:
{ "message": "API Rate Limit Exceeded for 112.199.99.5" }