The admin side of the settings-reorg Webhooks item. Needs inbuxa-server #100 (POST /api/webhook/test); against a server without it, the button reports the failure.
The card: a saved webhook's page opens with Send a test event. The server sends one sample event of type webhook.test, with the saved settings, even while the webhook is off. The card says to save first when there are unsaved changes.
The result in words:
Delivered: the receiver answered 204 in 3 ms.
Not accepted: the receiver answered 403. Check the sign-in details or signature key. (A 404 suggests checking the URL.)
Not delivered:
Checked:
A unit test for the wording. 503 tests pass in total.
Typecheck and lint are clean.
In Chrome against a local server built from #100: I created a webhook pointing at a local HTTP receiver and pressed Send test. The card showed Delivered: the receiver answered 204 in 3 ms. The receiver got the webhook.test event with X-Inbuxa-Test: true and the JSON content type.
English only: 4 new strings, plus the result sentences, which are English like the alert summaries.
The admin side of the settings-reorg Webhooks item. **Needs inbuxa-server #100** (`POST /api/webhook/test`); against a server without it, the button reports the failure.
- **The card:** a saved webhook's page opens with *Send a test event*. The server sends one sample event of type `webhook.test`, with the saved settings, even while the webhook is off. The card says to save first when there are unsaved changes.
- **The result in words:**
- *Delivered: the receiver answered 204 in 3 ms.*
- *Not accepted: the receiver answered 403. Check the sign-in details or signature key.* (A 404 suggests checking the URL.)
- *Not delivered: <reason>*
**Checked:**
- A unit test for the wording. 503 tests pass in total.
- Typecheck and lint are clean.
- In Chrome against a local server built from #100: I created a webhook pointing at a local HTTP receiver and pressed *Send test*. The card showed *Delivered: the receiver answered 204 in 3 ms*. The receiver got the `webhook.test` event with `X-Inbuxa-Test: true` and the JSON content type.
English only: 4 new strings, plus the result sentences, which are English like the alert summaries.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The admin side of the settings-reorg Webhooks item. Needs inbuxa-server #100 (
POST /api/webhook/test); against a server without it, the button reports the failure.webhook.test, with the saved settings, even while the webhook is off. The card says to save first when there are unsaved changes.Checked:
webhook.testevent withX-Inbuxa-Test: trueand the JSON content type.English only: 4 new strings, plus the result sentences, which are English like the alert summaries.