Webhook "Test Delivery" silently drops some "Custom Events" #3737

New Issue

GiteaMirror · 2025-11-02T05:23:46-06:00

GiteaMirror commented

2025-11-02 05:23:46 -06:00

Originally created by @gim on GitHub (Aug 6, 2019).

Gitea version (or commit ref): 1.8.3
Git version: 2.22.0
Operating system: Arch
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite

Description

I attempted to create a Webhook for a new repository that posted to Discord.

As the very first measure after I registered the Webhook I used the 'Test Delivery' button at the bottom right of the 'Update Webhook' form to ensure that the system worked. However, no events were ever forwarded, and the 'Recent Deliveries' list remained empty. (I also tested that no events were posted by substituting the 'Target URL' for an address I control)

When I recreated the Webhook and specified "All Events" rather than "Custom Events" the 'Test Delivery' button worked as expected (using the original 'Target URL').

It feels like this may have occurred because I set the 'Custom Events' to be 'Issues' and 'Issue Comment' only, and the test message posted is "This is a fake commit".

If the above is correct: perhaps it would be worth bypassing the filters, issuing a warning, or tailoring the test message?

Originally created by @gim on GitHub (Aug 6, 2019). - Gitea version (or commit ref): 1.8.3 - Git version: 2.22.0 - Operating system: Arch - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite ## Description I attempted to create a Webhook for a new repository that posted to Discord. As the very first measure after I registered the Webhook I used the 'Test Delivery' button at the bottom right of the 'Update Webhook' form to ensure that the system worked. However, no events were ever forwarded, and the 'Recent Deliveries' list remained empty. (I also tested that no events were posted by substituting the 'Target URL' for an address I control) When I recreated the Webhook and specified "All Events" rather than "Custom Events" the 'Test Delivery' button worked as expected (using the original 'Target URL'). It feels like this may have occurred because I set the 'Custom Events' to be 'Issues' and 'Issue Comment' only, and the test message posted is "This is a fake commit". If the above is correct: perhaps it would be worth bypassing the filters, issuing a warning, or tailoring the test message?

GiteaMirror added the issue/stale type/bug labels 2025-11-02 05:23:46 -06:00

GiteaMirror closed this issue

2025-11-02 05:23:46 -06:00

GiteaMirror commented

2025-11-02 05:23:47 -06:00

@lafriks commented on GitHub (Aug 6, 2019):

I think there was issue for this as currently test button only works for git push events

@lafriks commented on GitHub (Aug 6, 2019): I think there was issue for this as currently test button only works for git push events

GiteaMirror commented

2025-11-02 05:23:47 -06:00

@stale[bot] commented on GitHub (Oct 5, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Oct 5, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:23:47 -06:00

@stale[bot] commented on GitHub (Oct 19, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Oct 19, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#3737