{"push_id":2447425039,"size":2,"distinct_size":0,"ref":"refs/heads/master","head":"2b18d40babe3f1b6d9609172a02c90f64c172a26","before":"91b13b10b9b5f0fa32454a4249de26936c72a201","commits":[{"sha":"2e0e9cd68f0dd462a61a353129ac720b16b7883b","author":{"name":"Remi Broemeling","email":"f977fbb3de5c2ff040c80bd495d499b604e86839@clio.com"},"message":"Slightly improve Dyn provider error reporting. (#473)\n\nIf Dyn responds with a 3xx or 4xx status code, information describing exactly\r\nwhat went wrong is generally included in the body of the response (as part of\r\nthe typical Dyn JSON response). On the other hand, if Dyn responds with a 5xx\r\nstatus code, we very likely have extremely limited information.\r\n\r\nThis commit modifies the reporting to display the explanatory messages included\r\nin the body of the Dyn response for 3xx and 4xx status codes. The intent is to\r\nmake it much easier to determine what might be going wrong (when something is\r\ngoing wrong).","distinct":false,"url":"https://api.github.com/repos/abjugard/lego/commits/2e0e9cd68f0dd462a61a353129ac720b16b7883b"},{"sha":"2b18d40babe3f1b6d9609172a02c90f64c172a26","author":{"name":"Alexander Neumann","email":"46ca6bb66dd1ddd677696c7fc0ad6610b856e758@users.noreply.github.com"},"message":"Add DNS challenge provider 'exec' (#508)\n\nAs discussed in #505, this commits adds a very simple DNS provider which\r\ncalls out to an external program which must then add or remove the DNS\r\nrecord.","distinct":false,"url":"https://api.github.com/repos/abjugard/lego/commits/2b18d40babe3f1b6d9609172a02c90f64c172a26"}]}
{"actor":{"display_login":"abjugard"}}