fix: Discord #recent-activities webhook delivery (empty meta/username)
This commit is contained in:
parent
4b5b098464
commit
a9f25945ad
1 changed files with 11 additions and 0 deletions
|
|
@ -61,3 +61,14 @@ Each important update should include:
|
||||||
|
|
||||||
- Test delivery succeeded on all 4 repo webhooks.
|
- Test delivery succeeded on all 4 repo webhooks.
|
||||||
- This commit serves as the first real push-event test of the integration.
|
- This commit serves as the first real push-event test of the integration.
|
||||||
|
|
||||||
|
### Fixed
|
||||||
|
|
||||||
|
- Discord deliveries were silently failing for every webhook: each
|
||||||
|
webhook's `meta` config was empty, which broke Forgejo's Discord
|
||||||
|
payload builder (invalid JSON, then Discord rejected the empty
|
||||||
|
`username` field). Set a valid `username` ("KiteStacks Forgejo") on
|
||||||
|
all 4 webhooks.
|
||||||
|
- Re-ran test deliveries on all 4 repos - all returned 204 from Discord.
|
||||||
|
- This push is the first real end-to-end delivery confirming
|
||||||
|
#recent-activities now receives live Forgejo push notifications.
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue