{"push_id":1131367861,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"b30a8ff0fda83b7dc120da0378a2375dad55d7e2","before":"55ee8e02447e54c6fb048ea3e21868b476a1e43c","commits":[{"sha":"8376089e6274c8883812075128d6575b322d810f","author":{"name":"Eric Anderson","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"Move `current_ability` into it's own module.\n\nA common need is to render alchemy content within the another context\n(the app or another engine). An example of this would be the alchemy-solidus\ngem. We do this by included `Alchemy::ControllerActions` into the controllers\nfor the context we want to use the Alchemy content in.\n\nThe problem is when this is done IF that gem is also using cancancan (like\nSolidus does) then the `current_ability` method from Alchemy can end up\noverwritting the `current_ability` of the controller doing the including.\n\nBy moving `current_ability` to it's own module it allows the including\ncontroller to decide if that method is desired or not.","distinct":true,"url":"https://api.github.com/repos/AlchemyCMS/alchemy_cms/commits/8376089e6274c8883812075128d6575b322d810f"},{"sha":"b30a8ff0fda83b7dc120da0378a2375dad55d7e2","author":{"name":"Martin Meyerhoff","email":"da39a3ee5e6b4b0d3255bfef95601890afd80709"},"message":"Merge pull request #1028 from eric1234/separate-auth-module\n\nMove `current_ability` into it's own module.","distinct":true,"url":"https://api.github.com/repos/AlchemyCMS/alchemy_cms/commits/b30a8ff0fda83b7dc120da0378a2375dad55d7e2"}]}
{"actor":{"display_login":"mamhoff"}}