-
Notifications
You must be signed in to change notification settings - Fork 9
Client Payload too large #23
Copy link
Copy link
Open
Description
Hi @mvasigh,
First of all, thanks a lot for this action, I use it quite often.
However, I have the following issue:
the action failes with the following error:
at /home/runner/work/_actions/mvasigh/dispatch-action/1.1.6/dist/index.js:9423:31
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async main (/home/runner/work/_actions/mvasigh/dispatch-action/1.1.6/dist/index.js:9217:23) {
status: 422,
[...]
I trigger it when a release is created and on workflow_dispatch:
on:
release:
types:
- published
workflow_dispatch:workflow_dispatch works fine, but when I create a release and upload all my assets (which are about 70), the client_payload is so large that the dispatch event is rejected.
Could you add an option to disable the client_payload field or to set it to null / {}?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels