User tests: Successful: Unsuccessful:
Adds in the same changes as in #682 for the other two hook controllers
I just discovered that, depending on the servers error reporting settings, the application does in fact provide some kind of errm... error response. E.g. for the initial "ping" event that is sent from GitHub, one might get a
{"data":{},"error":"Undefined property: stdClass::$issue","message":""}
Obviously this goes with a 200 status code...
200
I think we should improve our error reporting. We are relying 100% on valid data received from GitHub.
Can we redo this PR without altering the workflow?
Outdated. Webhook handlers have been updated a bunch since this PR.
I just discovered that, depending on the servers error reporting settings, the application does in fact provide some kind of errm... error response.
E.g. for the initial "ping" event that is sent from GitHub, one might get a
Obviously this goes with a
200status code...I think we should improve our error reporting. We are relying 100% on valid data received from GitHub.
Can we redo this PR without altering the workflow?