{"push_id":3472185376,"size":1,"distinct_size":1,"ref":"refs/heads/sg/debug-release","head":"4b9143244edea767a18df73a19a6e7de139c91aa","before":"0ec5ae64ac5e29f56e82b0d93533c477a6b55368","commits":[{"sha":"4b9143244edea767a18df73a19a6e7de139c91aa","author":{"name":"Stephen Gutekanst","email":"aef13f2c0474276f1af5f23465b7eed1b207df56@gmail.com"},"message":"Add support for publishing debug releases\n\nThis PR adds CI functionality so that pushing a branch `docker-images-debug/foobar`\nwill cause Docker images to be published with the tag `debug-foobar-$COMMIT`.\nThese published and tagged images can then be used to test e.g. a specific PR\non a real cluster instance.\n\nContext:\n\nAs part of PR #2884 I wanted to test my change on a real, large cluster\ninstance of Sourcegraph.\n\nThe only way for me to get CI to publish the images needed for doing this\ncurrently was to tag an actual release candidate like `v3.3.0-debug.0` but in\nmy mind this is wrong to do because that looks like it actually corresponds to\nthe version 3.3.0 when in reality my change is just arbitrary and not directly\na statement of releasing a version (as cutting a release candidate may be, for\nexample).","distinct":true,"url":"https://api.github.com/repos/sourcegraph/sourcegraph/commits/4b9143244edea767a18df73a19a6e7de139c91aa"}]}
{"actor":{"display_login":"slimsag"}}