From 58b6bbbb3a8fa973bc9e2ab5925d19bcff11e18b Mon Sep 17 00:00:00 2001 From: Sebastian Mendel Date: Fri, 14 Aug 2026 15:24:25 +0200 Subject: [PATCH] [TASK] Webhook: how to read the delivery responses on GitHub Document the delivery response codes shown under Recent Deliveries (200 ping, 204 render triggered, 412 not yet approved - expected before Documentation Team approval) and that branch and tag pushes are separate deliveries: where to look when a new version does not appear. GitLab and Bitbucket expose the same information in their webhook edit views. Assisted-by: Claude Fable 5 Signed-off-by: Sebastian Mendel --- .../Howto/WritingDocForExtension/Webhook.rst | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/Documentation/Howto/WritingDocForExtension/Webhook.rst b/Documentation/Howto/WritingDocForExtension/Webhook.rst index e9fe593b..72b49e62 100644 --- a/Documentation/Howto/WritingDocForExtension/Webhook.rst +++ b/Documentation/Howto/WritingDocForExtension/Webhook.rst @@ -229,6 +229,24 @@ To set up a GitLab webhook: .. figure:: /_Images/webhook/gitlab/intercept-feedback.png :width: 932 +.. _webhook-deliveries: + +Reading the webhook deliveries on GitHub +======================================== + +In the GitHub repository settings under :guilabel:`Webhooks > Recent +Deliveries` every delivery shows the response of the documentation server: + +* `200`: ping accepted. +* `204`: push accepted, a rendering was triggered. +* `412`: repository not approved yet — expected for the first test + delivery before the Documentation Team has approved the project. + +A branch push and a tag push are separate deliveries. When a new version does +not appear on docs.typo3.org, check the delivery of the **tag** push — the +branch push having succeeded says nothing about the tag. GitLab and Bitbucket +show the corresponding information in their webhook edit views. + .. _webhook-testing: Testing webhooks