Webhook payloads sent from DoltHub and DoltLab have differing properties depending on the event type, and it's kinda confusing. There's no simple way to determine what type of event is was sent, and writing a server to handle events based on which field is present/missing from the payload isn't really how other webhook models work. Or at least, there's a set of properties common to all payloads that help webhook servers direct the payload to the right handler.
I think we should follow github here define a set of common properties found in all payloads. Then, if a specific events needs additional fields, those can be added as well.
The goal here would to make the webhook payloads a bit easier/simpler to work with.
Webhook payloads sent from DoltHub and DoltLab have differing properties depending on the event type, and it's kinda confusing. There's no simple way to determine what type of event is was sent, and writing a server to handle events based on which field is present/missing from the payload isn't really how other webhook models work. Or at least, there's a set of properties common to all payloads that help webhook servers direct the payload to the right handler.
I think we should follow github here define a set of common properties found in all payloads. Then, if a specific events needs additional fields, those can be added as well.
The goal here would to make the webhook payloads a bit easier/simpler to work with.