Send complete event

[thspinto]

☕ Purpose

Send complete github event in client_payload.data at createEventDispatch.

🔍 Use cases

I'd like to run sonarscanner to check for code health globally in the organization. For this I need metadata such as the PR number. I thought it would be best to send everything since I sure I'll have a use case for other infos in the future.

[SvanBoxel]

I think this would be a really great improvement, so thank you! 💯

What I'm however a bit worried about is backwards compatibility. There are users that leverage the client_payload.sha and client_payload.repository.owner data and changing this will break at least a handful of workflows. Could we instead add a payload or data property to the current payload that includes all event data?

[thspinto]

I liked the idea!

Updated the PR using the client_payload.data field. Also added this information to the README.

[SvanBoxel]

Love it and we're almost there. I requested a couple of minor changes and then we're good to go. 🚀

[SvanBoxel]

I think naming is a bit confusing because we use the spread operator on data on line 67. I wouldn't use a variable and a object property within the same context if they have a different value. Could we either rename the object property or otherwise the data variable?

[thspinto]

I renamed it to event. I thought about origin_eventor original_event, but I think that in the context of a repository dispatch just event shouldn't be misleading.

[SvanBoxel]

🚢

[SvanBoxel]

Release with 1.3.0.