{"push_id":2958532275,"size":1,"distinct_size":1,"ref":"refs/heads/dokku-inspect","head":"15a2b7cbce9db8f663f04eb046894f6eff722a99","before":"55b3f7f1f9587abbe014b61d6027b5bb4609c983","commits":[{"sha":"15a2b7cbce9db8f663f04eb046894f6eff722a99","author":{"name":"Jose Diaz-Gonzalez","email":"a88b7dcd1a9e3e17770bbaa6d7515b31a2d7e85d@josediazgonzalez.com"},"message":"feat: sanitize docker inspect output with ps:inspect\n\nOften-times, we will want to have the container inspect output for debugging purposes, but this process is:\n\n- error prone, as the user needs to know what their containers are\n- potentially insecure, as the output must be sanitized of sensitive data\n\nInstead of making users wade through this process, we provide a helper `ps:inspect` command, that can be used to diagnose problems associated with containers that may or may not exist for an application.","distinct":true,"url":"https://api.github.com/repos/dokku/dokku/commits/15a2b7cbce9db8f663f04eb046894f6eff722a99"}]}
{"actor":{"display_login":"josegonzalez"}}