Skip to content

[TASK] Webhook: how to read the delivery responses on GitHub #546

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
linawolf merged 1 commit into from
Aug 17, 2026
Merged

[TASK] Webhook: how to read the delivery responses on GitHub #546

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions Documentation/Howto/WritingDocForExtension/Webhook.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down