{"push_id":2422163031,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"5cd274b066de67b93d2620755a81e706b4f56d66","before":"d1e6c826609c0848dd7f5a4a8335d142df16dd55","commits":[{"sha":"5cd274b066de67b93d2620755a81e706b4f56d66","author":{"name":"Brandon Rhodes","email":"e390cae40d36eb7215a5d5c19d011c770c86dee1@dropbox.com"},"message":"Fixes following a Bazel upgrade on our end\n\nWe seem to be on a version of Bazel that now performs depth 1 checkouts\nbut that does not yet incorporate:\n\nhttps://github.com/bazelbuild/bazel/commit/6496b1d1d25025f33406b1eaf9949cab126f08bd\n\nthat would presumably let us make our checkouts a bit less shallow, and\nthus pin to arbitrary commits.  Instead, we must at the moment pin to\nactual tags and branches on GitHub.  This diff makes the changes\nnecessary to pin to available versions instead of arbitrary commits;\ntweaks a few things that broke during the necessary upgrades this\nentailed; and where appropriate, follows the current Bazel docs in\nreplacing git repository fetches with HTTP archives.\n\nThe one thing I don’t like is specifying “master” for the repository\n“org_pubref_rules_protobuf” — should we instead ask them to make a more\nrecent release?  Or fork the repository ourselves as a target?","distinct":true,"url":"https://api.github.com/repos/dropbox/livegrep/commits/5cd274b066de67b93d2620755a81e706b4f56d66"}]}
{"actor":{"display_login":"brandon-rhodes"}}