We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
A colleague pushed a change with many changed files/folders (87) to GitHub.
As the list of files is part of the webhook event, this had the effect that a quite large webhook event (request body) was delivered to smee.io.
The webhook type was a regular json and had a size of 156484 bytes.
I think it would be good for stability to also support larger pushes and increase the size to maybe 1MB.
Workaround: Push a smaller commit afterwards, then only the changes of the newer commit are part of the event.
Regards, Gernot
The text was updated successfully, but these errors were encountered:
GitHub can send payloads of up to 25MB 1
Smee is not meant to be used as a production service, it's to help facilitate during development.
Now, 25MB is definitely out of the question, 1MB payloads sound reasonable
Sorry, something went wrong.
Would also love to see the payload size increased, hitting the 413 pretty often while developing with smee.
No branches or pull requests
Hi,
A colleague pushed a change with many changed files/folders (87) to GitHub.
As the list of files is part of the webhook event, this had the effect that a quite large webhook event (request body) was delivered to smee.io.
The webhook type was a regular json and had a size of 156484 bytes.
I think it would be good for stability to also support larger pushes and increase the size to maybe 1MB.
Workaround: Push a smaller commit afterwards, then only the changes of the newer commit are part of the event.
Regards,
Gernot
The text was updated successfully, but these errors were encountered: