So, what I built here is actually a lot simpler than that.
This tool isn’t meant to sting, it’s only meant to coax you to use commits-to even more. I was talking with @dreev a couple of months ago about how I can do something for Commits.To, and one of the ideas he had was for a simplest possible integration, sort of what’s described in https://github.com/commitsto/commits.to/wiki#simple-beeminder-integration
It’s not strictly that. How this tool behaves, you get a point each time you make a commitment, and you get another point each time you complete one. (On-time, late, doesn’t matter. Everything is a point, so for each promise you commit and finish, two points.)
It runs on Kubernetes (or Heroku, but I’m using Kubernetes). So it’s very easy to game your beeminder goal, if you are running out of time and none of your open Commits are able to be completed before time runs out: just make another promise.
The goal for me here wasn’t really to make a seriously useful integration, I just wanted something that would put my Commits on a graph. Mostly this is how I always use Beeminder. “Just put it on a graph, and good things will happen after that.”
One way this could definitely be improved is by making a better guide for how to install it for yourself.
Another caveat is that this is developed against commits.to:master branch, which means that it’s scraping HTML. It could be improved by rebuilding it against the 2.0/develop branch, which has a real full-featured API, and it would no longer require scraping. Again I just wanted to get my commits on a graph, and practice some of my OO design skills a bit, so I haven’t done that yet. But it’s coming soon.
(And it’ll have to come sooner if 2.0 goes live in the near future, since scraping HTML with nokogiri definitely won’t work with the next version, from what I can tell.)