{"push_id":885329695,"size":1,"distinct_size":1,"ref":"refs/heads/publishing_apiV2","head":"ad3c5561a7f350ee329e73b2cc5c984f83b922c7","before":"e29a89d977eae5c890c69715599427682ae1c246","commits":[{"sha":"ad3c5561a7f350ee329e73b2cc5c984f83b922c7","author":{"email":"84607ab8e6b8852467ce0c2ec9c63ea8d5c40acc@digital.cabinet-office.gov.uk","name":"stephenrichards"},"message":"Use V2 of the publishing-api to write and publish content to the content store\n\nThis change modifies collections-publisher to use V2 of the publishing API (see\nhttps://gov-uk.atlassian.net/wiki/display/TECH/Publishing+Platform?focusedCommentId=42303704#comment-42303704 for details).\n\nThe usage of the API is abstracted by use of the gds-api-adapters gem.  The main differences are:\n - a content_id is the main identifier of content being written to the content store, rather than base path\n - a simple put_content will write the content item to the draft content store\n - a subsequent publish is required to write the cotnetn item to the live content store\n - archiving a topic is achieved by replacing the existing topic with a redirect item with the same content_id, and then publishing it.","distinct":true,"url":"https://api.github.com/repos/alphagov/collections-publisher/commits/ad3c5561a7f350ee329e73b2cc5c984f83b922c7"}]}