-
Notifications
You must be signed in to change notification settings - Fork 41
fix: add event examples with installation key that don't have them yet #195
New issue
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
fix: add event examples with installation key that don't have them yet #195
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove the example payloads for installation
and installation_repositories
that don't have the installation
key. Also the installation always has a node_id
which is a string besides the id
key
"type": "User", | ||
"site_admin": false | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The installation_repositories
event has always the installation
key.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I doubted about this one because, according to docs, it says
The GitHub App installation. Webhook payloads contain the installation property when the event is configured for and sent to a GitHub App.
If it's like this, I'm going to PR to Github Docs :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
go PR the docs, I'm very sure that "installation"
is always present for these two particular events. They will let us know if otherwise. You can reference this PR
"type": "User", | ||
"site_admin": false | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The installation
event has always an installation key
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I doubted about this one because, according to docs, it says
The GitHub App installation. Webhook payloads contain the installation property when the event is configured for and sent to a GitHub App.
If it's like this, I'm going to PR to Github Docs :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case the "installation"
object is the key part of the payload, it has many properties beyond just id
and node_id
. I'm sure that it's always present
β¦llation' until this issue is clarified github/docs#516
β¦nstallation' prop
Removed Once Github Docs provides feedback, a separate PR would be opened in case it's necessary to tackle |
Great work! |
π This PR is included in version 3.18.3 π The release is available on: Your semantic-release bot π¦π |
Confirmed by Github Docs team. The property is there 100% so no need to do a followup PR :) |
π Summary
Add
installation
optional paramater to Webhook Payloads missing it.β± Motivation and Context
octokit/webhooks.js#266
Fix #198