{"push_id":764487100,"size":2,"distinct_size":0,"ref":"refs/heads/deployed-to-preview","head":"0a9054a48b5a980ebaf7958e360c2a448ed716b2","before":"b1b3df8eb5cdf748c5f5192c4dfb7104e00581fa","commits":[{"sha":"26e1c38946f3c0335f590b7837f9100ff02c9838","author":{"email":"be8758dc4a66004612e74b567a662d4f1fbf4c2e@gmail.com","name":"tijmen"},"message":"Don't request `last_update` from rummager\n\n`public_timestamp` is exactly equivalent to `last_update`, because\nrummager indexes it from `last_update` whenever `public_timestamp` is\nmissing.\n\nMore backstory:\n\n> Historically, public_timestamp was populated by documents from\nwhitehall, and last_update was populated by documents from\nspecialist-publisher. We noticed the duplication when implementing the\nrummager schemas, and made specialist-publisher populate both fields,\nwith an aim to remove the last_update field at some point - but never\ngot to the point where we're certain that nothing is still using the\nlast_update field.\n\nhttps://github.com/alphagov/hmrc-manuals-api/pull/94#discussion_r3661067\n9\n\nThis commit makes sure that frontend doesn't use the old field anymore,\nso we can remove it from rummager later.","distinct":false,"url":"https://api.github.com/repos/alphagov/frontend/commits/26e1c38946f3c0335f590b7837f9100ff02c9838"},{"sha":"0a9054a48b5a980ebaf7958e360c2a448ed716b2","author":{"email":"d44b6537b4a214e92da5b6fd78d5b10cc5ef0bda@gmail.com","name":"Kushal Pisavadia"},"message":"Merge pull request #864 from alphagov/remove-last-update\n\nDon't request `last_update` from rummager","distinct":false,"url":"https://api.github.com/repos/alphagov/frontend/commits/0a9054a48b5a980ebaf7958e360c2a448ed716b2"}]}