{"push_id":1572288576,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"ac01be92ce0f41cf3e85d7b825d01d340facc4a1","before":"7a3d204f34781417e65806c6bd12196b804ef81d","commits":[{"sha":"a12011aa01564227f934d170c2563a544eaf20b9","author":{"name":"Luke Lee","email":"fe6a0b9b5aee2bd901f54ad4992feac186586a50@gmail.com"},"message":"Fix bug with only caching rendered article content\n\n- Previously we were only caching guides with their rendered text to save on\n  cache space.  However, we changed this in aef16ae23.  We now do all the\n  markdown rendering on the front-end because it saves an extra github API\n  request.  Unfortunately, we never changed our caching strategy to cache\n  guides if we didn't render their content first.","distinct":true,"url":"https://api.github.com/repos/pluralsight/guides-cms/commits/a12011aa01564227f934d170c2563a544eaf20b9"},{"sha":"ac01be92ce0f41cf3e85d7b825d01d340facc4a1","author":{"name":"Luke Lee","email":"fe6a0b9b5aee2bd901f54ad4992feac186586a50@gmail.com"},"message":"Cache published guides for a maximum of 2 hours and refresh on push webhooks\n\n- We were already using the webhooks to delete guides from the cache but now\n  we'll force a re-read of any published guides to refresh in the background\n  instead of waiting for the next read.  This should make the front-end reading\n  of published guides use the cache as efficiently as possible since most times\n  that request won't have to hit the Github API","distinct":true,"url":"https://api.github.com/repos/pluralsight/guides-cms/commits/ac01be92ce0f41cf3e85d7b825d01d340facc4a1"}]}
{"actor":{"display_login":"durden"}}