Refactor GitHub webhook handler to have a case for each event of interest #3359

blkt · 2024-05-17T15:10:18Z

Currently, the GitHub webhook handler treats different event types uniformly and the "dispatch logic" for each event is spread over multiple routines. This makes it harder to extend the logic in case new events need to be handled.

Refactor the handler so that every event type has its own routine implementing the necessary business logic.

…ation. The idea is to make it easier to extend github webhook with events that are tied to more than one repository, namely "installation" and "installation_repositories", which are necessary for repo auto registration. Fixes #3359

…ation. (#3346) The idea is to make it easier to extend github webhook with events that are tied to more than one repository, namely "installation" and "installation_repositories", which are necessary for repo auto registration. Fixes #3359

blkt self-assigned this May 20, 2024

blkt mentioned this issue May 21, 2024

Make github webhook easier to extend with new events for auto registration. #3346

Merged

10 tasks

blkt closed this as completed in #3346 May 30, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Refactor GitHub webhook handler to have a case for each event of interest #3359

Refactor GitHub webhook handler to have a case for each event of interest #3359

blkt commented May 17, 2024 •

edited

Loading

Refactor GitHub webhook handler to have a case for each event of interest #3359

Refactor GitHub webhook handler to have a case for each event of interest #3359

Comments

blkt commented May 17, 2024 • edited Loading

blkt commented May 17, 2024 •

edited

Loading