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, I noticed the following documentation on GitHub#parseEventPayload:
GitHub#parseEventPayload
[...] Unfortunately, hook script payloads aren't self-descriptive, so you need to know the type of payload you are expecting.
As far as I see, the event type is present within x-github-event header of the incoming hook request.
x-github-event
As stated here:
I've checked the request and the event name does really match the ones available on the aforementioned page.
Could we match the event type strings to GHEventPayload implementations so we don't have to provide the type?
GHEventPayload
P.S. Thanks for the great library! ❤️
The text was updated successfully, but these errors were encountered:
I might be able to raise a PR if you're interested.
Sorry, something went wrong.
No branches or pull requests
Hi, I noticed the following documentation on
GitHub#parseEventPayload
:As far as I see, the event type is present within
x-github-event
header of the incoming hook request.As stated here:
I've checked the request and the event name does really match the ones available on the aforementioned page.
Could we match the event type strings to
GHEventPayload
implementations so we don't have to provide the type?P.S. Thanks for the great library! ❤️
The text was updated successfully, but these errors were encountered: