{"push_id":1023675221,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"1104cc365e715ecbb232c19a306d68fa8d6b8013","before":"bcdcbe3fb3c6af5aba87d9d758d7c46501549098","commits":[{"sha":"3bcf020c2e74e34a169eefa04fd58ed140fed6a7","author":{"email":"55b60a8aae5830b491c6a2f9b782fd8592cbb009@gmail.com","name":"Blake Pettersson"},"message":"One select to rule them all,\n\nOne select to find them, one select to bring them all and in the\ndarkness bind them.\n\nThis commit consolidates all the various kinds of selects that we\nhave previously had into one single component - ultimate-select.\n\n(The name can be debated and of course changed, but in lieu of a\nbetter one..)\n\nThe ultimate-select basically works the same way as the former\nprimitive-select and object-select did. To work with object\ncollections, you choose the key and value by specifiying itemKey\nand itemValue respectively. This works with both POJOs and Ember\nobjects. For primitive types, don't specify itemKey and itemValue\nand it should work just like primitive-select.\n\nAFAICS this also removes all usages of Ember views, and now we're\njust using components \\o/","distinct":true,"url":"https://api.github.com/repos/aptible/dashboard.aptible.com/commits/3bcf020c2e74e34a169eefa04fd58ed140fed6a7"},{"sha":"1104cc365e715ecbb232c19a306d68fa8d6b8013","author":{"email":"6794d21b82ccbc26c3c80f0d4976a76ab0446ad7@aptible.com","name":"Skylar Anderson"},"message":"Merge pull request #549 from blakepettersson/select-consolidation\n\nOne select to rule them all,","distinct":true,"url":"https://api.github.com/repos/aptible/dashboard.aptible.com/commits/1104cc365e715ecbb232c19a306d68fa8d6b8013"}]}