{"push_id":984137789,"size":1,"distinct_size":1,"ref":"refs/heads/export-hubot-without-dynamic-loading","head":"48f3f8bbc1243a53a42ea847b369a401f3ea136d","before":"da5581e5889649bd16ce10756d7e16f12e93f0be","commits":[{"sha":"48f3f8bbc1243a53a42ea847b369a401f3ea136d","author":{"email":"d20cef1de2369697fa578500daa5391b2aef5ae6@gmail.com","name":"Jack Lawson"},"message":"Split robot into smaller bits\n\nRefactor hubot into three parts:\n\n* One class which manages the autoloading of scripts and http server,\n  which subclasses:\n* Another class that manages the running of scripts, event emitter, and\nother core functionality\n* express.coffee, which contains functionality to create the web server\n\nThe purpose of this is so that one can use the \"basebot\" for all of\nhubot's functionality, without having to also require autoloading of\nfiles. For example, one may want to precompile hubot + scripts into a\nsingle, dead-code-eliminated javascript file for lower memory usage and\nstartup time.\n\nThere should be no user-facing changes to how hubot works. (It does expose\nthe additional ability to define your own router easily if you prefer\nto use something other than express.)\n\nWe could also call basebot \"batteries\" or something clever.","distinct":true,"url":"https://api.github.com/repos/ajacksified/hubot/commits/48f3f8bbc1243a53a42ea847b369a401f3ea136d"}]}