{"push_id":1139349972,"size":2,"distinct_size":1,"ref":"refs/heads/master","head":"36c56e6e2daf1af86ba297d977b6b6021e5ff374","before":"4befd0eeed5cd690cef805681bf36ce66d27f7f6","commits":[{"sha":"c4b25043f7bfd12dc5b7a674d7a4c8fdccf9269c","author":{"name":"Leonardo Crauss Daronco","email":"21407852535de1062719dbd5fbf5620bb147cc8e@gmail.com"},"message":"Fix how recent activities are created for meetings\n\nOne error is that it was trying to get information from the controller,\nbut since meetings are usually created from models/workers, the controller\nwould be nil. This fixes issue #861.\n\nThere were tests to make sure the RA was correct, but they would always\npass if running after controller tests, and that's why the error was not\ndetected before.\n\nUpdating the gem public_activity fixed the conflicts in the tests.\nWith the update, also disabled recent activity creation by default for all\ntests (expect on features and workers), which improves performance a bit.\nNow tests that require activities have to require them explicitly.","distinct":false,"url":"https://api.github.com/repos/mconf/mconf-web/commits/c4b25043f7bfd12dc5b7a674d7a4c8fdccf9269c"},{"sha":"36c56e6e2daf1af86ba297d977b6b6021e5ff374","author":{"name":"Leonardo Crauss Daronco","email":"21407852535de1062719dbd5fbf5620bb147cc8e@gmail.com"},"message":"Merge pull request #862 from mconf/issue861-fix-recent-activity-for-meetings\n\nFix how recent activities are created for meetings","distinct":true,"url":"https://api.github.com/repos/mconf/mconf-web/commits/36c56e6e2daf1af86ba297d977b6b6021e5ff374"}]}
{"actor":{"display_login":"daronco"}}