{"push_id":2932191730,"size":1,"distinct_size":1,"ref":"refs/heads/dont-tell-the-publishing-api-the-wrong-first-published-at-time","head":"fba3061de4dadd2bcb53e8a4be009317e50915eb","before":"1ab52e957e8bebddecfe91dd74de3f2b28afaf58","commits":[{"sha":"fba3061de4dadd2bcb53e8a4be009317e50915eb","author":{"name":"Christopher Baines","email":"c14e4e2094dd20d1d0dcfc7ec4547168bcc89be2@digital.cabinet-office.gov.uk"},"message":"Add data migration to fix first_published_at values\n\nAlong with the first_public_at values for scheduled content which\nhasn't been published yet.\n\nThis is necessary, as Whitehall has been sending the\nfirst_published_at values for content which hasn't been published\nyet... and it didn't even get them right for scheduled content (even\nthough the value would have been in the future!).\n\nThis is a copy of the previous\n20181002120423_create_publishing_api_drafts_for_scheduled_content.rb\nmigration to do the same thing for a different reason.","distinct":true,"url":"https://api.github.com/repos/alphagov/whitehall/commits/fba3061de4dadd2bcb53e8a4be009317e50915eb"}]}
{"actor":{"display_login":"cbaines"}}