payload: {"push_id":4143537688,"size":2,"distinct_size":0,"ref":"refs/heads/master","head":"bdb1365769b0ee211a4c279b379d84f795da5edf","before":"895c37c3bb0b430831586b8cd8190eab7bf63e1e","commits":[{"sha":"5d5fea5c8a714304eee3a26be5bc4a49e9bd041a","author":{"name":"Henry Van Styn","email":"cdbe776ce0e6c58186b910c478aaa21483f0ca47@intellitree.com"},"message":"Prelim design with pRender to invoke postprocess classes\n\nThis are meant to support rendering at-will using the postprocess\nback end class but as a simple in-line renderer called from template\ndirectives.\n\nStill experimental","distinct":false,"url":"https://api.github.com/repos/vanstyn/Rapi-Blog/commits/5d5fea5c8a714304eee3a26be5bc4a49e9bd041a"},{"sha":"bdb1365769b0ee211a4c279b379d84f795da5edf","author":{"name":"Henry Van Styn","email":"cdbe776ce0e6c58186b910c478aaa21483f0ca47@intellitree.com"},"message":"Working 'ppRender' API + add TextMarkdown post-processor\n\nFleshed out the new ppRender template directive which allows manually\npassing some arbitrary bit of content through a chosen post-processor.\n\nUp until now, there has been only one post-processor, MarkdownElement\nwhich relies on the marked.js client-side JavaScript library. This works\ngreat, but the downside is any location where this isn't available, such\nas in a news feed or a repost situation.\n\nMarkdownElement is still the default, but the new 'TextMarkdown' is now\navailable as well, and can be accessed via the new ppRender directive.\nTextMarkdown uses Text::Markdown, which is a pure pure implementation,\nbut is not as feature-rich as marked.js, doesn't know about GFM, etc.\n\nThe ways ppRender can be called are in source-code comments, still need\nto update the POD.\n\nSet dev version 1.1100_01","distinct":false,"url":"https://api.github.com/repos/vanstyn/Rapi-Blog/commits/bdb1365769b0ee211a4c279b379d84f795da5edf"}]}
other: {"actor":{"display_login":"vanstyn"}}