When receiving events via the Github Webhook, many of them contain “id” and “node_id” fields. Comparing to the GraphQL api, “id” is equivelant to “databaseId” and “node_id” is equivelant to “id”. That’s great. Knowing that, I can correlate data received via the webhooks with data that I’ve quiered via the graphql endpoint.
However, some events received via the webhooks contain no identifying information at all. For example, an issues assigned event simply references the issue, the assignee, and the sender (the user doing the assigning). Since a user can assign/unassign another user repeatedly, there is nothing that uniquely identifies that event for a given issue. If there was atleast an official timestamp sent with the event, we could haphazardly correlate it with data received via the graphql endpoint, but there isn’t even that.
So basically what I’ll be forced to do is when receiving these types of events via the webhook, I then have to requiry the issue/PR timeline via the graphql endpoint in order to retreive the necessary data. That defeats much of the purpose of the webhook in the first place.