{"push_id":1228247088,"size":1,"distinct_size":1,"ref":"refs/heads/trip-model-routes","head":"d27d2d75babe2ba0bbfe896d422e93292feffdeb","before":"b2ee88fddff9530255e18d25de8e8e250c7d4680","commits":[{"sha":"d27d2d75babe2ba0bbfe896d422e93292feffdeb","author":{"name":"Herman Ng","email":"9f55f9917b227dcfc3e29047beb4b7aff719fa37@gmail.com"},"message":"Change trip destination schema and add API routes\n\nInstead of storing trip destinations as a list of strings, we devise a\ncustom schema for each destination, allowing us to store a Google Place\nID, GPS coordinates, and the type of place. One example use case for\nthis data is to identify the bounding box to display a map of the trip\ndestinations for the user. [Finishes #127398901]","distinct":true,"url":"https://api.github.com/repos/heymanhn/journey-backend/commits/d27d2d75babe2ba0bbfe896d422e93292feffdeb"}]}
{"actor":{"display_login":"heymanhn"}}