The forge APIs all support webhooks for real-time event delivery, but the library has no webhook support.
Two possible scopes:
- Webhook management: Create/list/delete webhooks via the API (GitHub, GitLab, Gitea/Forgejo all have endpoints for this)
- Event parsing: Parse incoming webhook payloads into normalized event types, similar to how the library normalizes API responses across forges
Event parsing would be particularly useful since each forge has its own webhook payload format and event names. A unified event type system would let consumers handle webhook events without forge-specific code.
This could live alongside the existing polling-based NotificationService as an alternative real-time delivery mechanism.
The forge APIs all support webhooks for real-time event delivery, but the library has no webhook support.
Two possible scopes:
Event parsing would be particularly useful since each forge has its own webhook payload format and event names. A unified event type system would let consumers handle webhook events without forge-specific code.
This could live alongside the existing polling-based NotificationService as an alternative real-time delivery mechanism.