{"push_id":861254683,"size":10,"distinct_size":10,"ref":"refs/heads/master","head":"bd7b2177291697a665e4068501b3704200972467","before":"39ebb06baf0be6e629f639b9fec6c37b1b7f0fe3","commits":[{"sha":"92bdd7627f40fe26dc35a8416b9cfb5462e88b18","author":{"email":"0798ebecfb7bc4dfb9d0445c2fa030eb64e1fa1c@webthriftstore.com","name":"Doug Krugman"},"message":"docs(guide/Concepts): remove unused `refresh` property\n\nCloses #13257","distinct":true,"url":"https://api.github.com/repos/lgalfaso/angular.js/commits/92bdd7627f40fe26dc35a8416b9cfb5462e88b18"},{"sha":"7da22e66855b5794d12d0e99e44f0c6f52ce2d55","author":{"email":"82848f870acf225368925a997f5307e2a6364292@googlemail.com","name":"Martin Staffa"},"message":"chore(docs): improve layout of search results\n\nThe API section now uses a multi-column list. This preserves the actual\norder of items. Note that only browser that support @supports and\ncolumns get the new behavior.\nThe line-breaking behavior of search results is also improved. Previously,\nlong words would break onto new lines or run into the second column.","distinct":true,"url":"https://api.github.com/repos/lgalfaso/angular.js/commits/7da22e66855b5794d12d0e99e44f0c6f52ce2d55"},{"sha":"0efef2385fe4dd4b2d72a964b1cf855c71733b4f","author":{"email":"82848f870acf225368925a997f5307e2a6364292@googlemail.com","name":"Martin Staffa"},"message":"chore(docs): display search result areas in a fixed order","distinct":true,"url":"https://api.github.com/repos/lgalfaso/angular.js/commits/0efef2385fe4dd4b2d72a964b1cf855c71733b4f"},{"sha":"077ee379426f29a082b6d6a737e1af8c68a40b83","author":{"email":"82848f870acf225368925a997f5307e2a6364292@googlemail.com","name":"Martin Staffa"},"message":"docs(changelog, migration): add BC notice for setting ngOptions as attribute\n\nCaused by 7fda214c4f65a6a06b25cf5d5aff013a364e9cef\n\nCloses #13145","distinct":true,"url":"https://api.github.com/repos/lgalfaso/angular.js/commits/077ee379426f29a082b6d6a737e1af8c68a40b83"},{"sha":"aff74ec87bd31933565b76cd0ab0b988cd9bae21","author":{"email":"82848f870acf225368925a997f5307e2a6364292@googlemail.com","name":"Martin Staffa"},"message":"docs(changelog, migration): add BC notice for ngMessages evaluation\n\nIntroduced by\n\nCloses #11616\nCloses #12001","distinct":true,"url":"https://api.github.com/repos/lgalfaso/angular.js/commits/aff74ec87bd31933565b76cd0ab0b988cd9bae21"},{"sha":"b837fc3116e697aaf18977867a5defd9541f7f8c","author":{"email":"fecd25d518a6a2ffc9f83fa7fe70c20f88f314b7@jbedard.ca","name":"Jason Bedard"},"message":"refactor($compile): simplify multi element directive check\n\nPreviously, we would check if an attribute indicates a multi-element\ndirective, now we only do this check if the attribute name actually\nmatches the multi-element name pattern.\n\nCloses #12365","distinct":true,"url":"https://api.github.com/repos/lgalfaso/angular.js/commits/b837fc3116e697aaf18977867a5defd9541f7f8c"},{"sha":"1a98c0ee346b718b9462da1abf4352a4605cbc7f","author":{"email":"bbd5783f48be5e95a98de06ba4cf842d64aaa74a@gmail.com","name":"mzdunek93"},"message":"fix($compile): fix scoping of transclusion directives inside replace directive\n\nCloses #12975\nCloses #12936\nCloses #13244","distinct":true,"url":"https://api.github.com/repos/lgalfaso/angular.js/commits/1a98c0ee346b718b9462da1abf4352a4605cbc7f"},{"sha":"1c13a4f45ddc86805a96576b75c969ad577b6274","author":{"email":"1d3764b91b902f6b45836e2498da81fe35caf6d6@torbicki.com","name":"Jakub Torbicki"},"message":"fix($compile): bind all directive controllers correctly when using `bindToController`\n\nPreviously only the first directive's controller would be bound correctly.\n\nCloses #11343\nCloses #11345","distinct":true,"url":"https://api.github.com/repos/lgalfaso/angular.js/commits/1c13a4f45ddc86805a96576b75c969ad577b6274"},{"sha":"50557a6cd329e8438fb5694d11e8a7d018142afe","author":{"email":"030f84cfc4d6c5fb82e5efeca9a248a2163d761a@hotmail.com","name":"Georgios Kalpakas"},"message":"fix($compile): evaluate against the correct scope with bindToController on new scope\n\nPreviously, the directive bindings were evaluated against the directive's\nnew (non-isolate) scope, instead of the correct (parent) scope.\nThis went unnoticed most of the time, since a property would be eventually\nlooked up in the parent scope due to prototypal inheritance. The incorrect\nbehaviour was exhibited when a property on the child scope was shadowing\nthat on the parent scope.\n\nThis commit fixes it.\n\nFixes #13021\nCloses #13025","distinct":true,"url":"https://api.github.com/repos/lgalfaso/angular.js/commits/50557a6cd329e8438fb5694d11e8a7d018142afe"},{"sha":"bd7b2177291697a665e4068501b3704200972467","author":{"email":"e3b6cda228242c30b711ac17cb264f1dbadfd0b6@bacondarwin.com","name":"Peter Bacon Darwin"},"message":"fix($compile): bind all directive controllers correctly when using `bindToController`\n\nPreviously only the first directive's controller would be bound correctly.\n\nCloses #11343\nCloses #11345","distinct":true,"url":"https://api.github.com/repos/lgalfaso/angular.js/commits/bd7b2177291697a665e4068501b3704200972467"}]}