{"push_id":865428055,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"41610c3996d0c4a58a7ed3ceceb3dbb4d7f2acae","before":"b4a5c2834c99f35fb31377197303f59034c40412","commits":[{"sha":"0ae4678c5cbaec7acb01004eaa36edbbc1feae3c","author":{"email":"1250ecce2ceacd06c7067311587caba2b878e4d0@icloud.com","name":"Immortalin"},"message":"Merge pull request #1 from google/master\n\nUpdate with main repository","distinct":true,"url":"https://api.github.com/repos/google/blockly/commits/0ae4678c5cbaec7acb01004eaa36edbbc1feae3c"},{"sha":"ad7ec48e702c47d5d9b44e5005f290a32918c9b2","author":{"email":"1250ecce2ceacd06c7067311587caba2b878e4d0@icloud.com","name":"Immortalin"},"message":"Add support for google closure library\n\nWhen the closure library is installed by npm, it is named \"google-closure-library\", however it is named \"closure-library\" in build.py. When both blockly and closure are installed by npm, they are in the same folder so theoretically theoretically blockly should be able to build. Formatting and indentation might be a bit off as I edited this using the github editor. \r\n\r\nThis ```python\r\nsearch_paths = calcdeps.ExpandDirectories(\r\n      [\"core\", os.path.join(os.path.pardir, \"closure-library\")])\r\n``` might need further revision to account for the additional naming. Maybe a try statement?","distinct":true,"url":"https://api.github.com/repos/google/blockly/commits/ad7ec48e702c47d5d9b44e5005f290a32918c9b2"},{"sha":"41610c3996d0c4a58a7ed3ceceb3dbb4d7f2acae","author":{"email":"cd27914b3e1639dc94716bc9b53172951d133513@gmail.com","name":"Neil Fraser"},"message":"Merge pull request #207 from Immortalin/master\n\nAdd support for google closure library","distinct":true,"url":"https://api.github.com/repos/google/blockly/commits/41610c3996d0c4a58a7ed3ceceb3dbb4d7f2acae"}]}