Commit 403ea69
committed
Fix to expect correct response for workflow_dispatch
It looks like GitHub introduced a breaking change in the API response
for workflow_dispatch.
The API now returns `200 OK` with a response body, while both the
documentation[^1] and the SDK[^2] still expect the old `204 No Content`
response.
```ruby
workflow_run_id: 20363538233,
run_url: "https://api.github.com/repos/ubicloud/github-e2e-test-workflows/actions/runs/20363538233",
html_url: "https://github.com/ubicloud/github-e2e-test-workflows/actions/runs/20363538233"}
>
```
https://github.com/orgs/community/discussions/182272
[^1]: https://docs.github.com/en/rest/actions/workflows?apiVersion=2022-11-28#create-a-workflow-dispatch-event--status-codes
[^2]: https://github.com/octokit/octokit.rb/blob/ea3413c3174571e87c83d358fc893cc7613091fa/lib/octokit/client/actions_workflows.rb#L41-L431 parent ea3413c commit 403ea69
1 file changed
+2
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
36 | 36 | | |
37 | 37 | | |
38 | 38 | | |
39 | | - | |
| 39 | + | |
40 | 40 | | |
41 | 41 | | |
42 | | - | |
| 42 | + | |
43 | 43 | | |
44 | 44 | | |
45 | 45 | | |
| |||
0 commit comments