Currently the triggers seem to be GitHub only.
A Forgejo webhook cannot drive any of them.
Forgejo does send a Gitea-compatible X-Hub-Signature-256. so the HMAC check could pass, but src/triggers/github/webhook.ts then hard-requires body.installation.id and returns 400 without it.
Also Forgejo payloads have no installation object.
Furhtermore src/providers/github/client.ts hardcodes https://github.com and https://api.github.com with no GHE-style base-URL override.
Also related to the Forgejo/Gitea/Gogs integrations of Paseo (3525, 3516, 3515, 2435, 2477, 2478, 1616, 2172, 1913, 2337 3404, 681).
Currently the triggers seem to be GitHub only.
A Forgejo webhook cannot drive any of them.
Forgejo does send a Gitea-compatible
X-Hub-Signature-256. so the HMAC check could pass, butsrc/triggers/github/webhook.tsthen hard-requiresbody.installation.idand returns400without it.Also Forgejo payloads have no
installationobject.Furhtermore
src/providers/github/client.tshardcodeshttps://github.comandhttps://api.github.comwith no GHE-style base-URL override.Also related to the Forgejo/Gitea/Gogs integrations of Paseo (3525, 3516, 3515, 2435, 2477, 2478, 1616, 2172, 1913, 2337 3404, 681).