Webhook

This section describes how to add webhooks for auto rendering to a repository.

The system currently supports Git as VCS (Version Control System), and the following hosters:

If none of the above is used, a mirror to one of these is recommend. Also the Documentation Team can setup custom hostings.

The following chapters provide illustrated walkthrough tutorials on how to add the necessary hook in those systems.

Legacy webhook

If the repository already had a hook, this is considered deprecated. A compatibility layer is still in place, but will be removed in the future.

An update is necessary.

GitHub

Add auto rendering for a repository via GitHub webhook in five steps:

  1. Go to “Settings” tab within the repository

  2. Go to “Webhooks” section within the repository settings

  3. Add webhook

  4. Fill in webhook configuration

    1. Configure URL https://docs-hook.typo3.org for field “Payload URL”.
    2. Select application/json as “Content type”.
    3. Enable “SSL verification”.
    4. Select Just the push event. for “Which events would you like to trigger this webhook?”.
    5. Enable “Activate”.
    6. Click on “Add webhook”
  5. Webhook was added

    GitHub should show a notice that creation of webhook was successful.

  6. (Optional) visit intercept and check request

    If curious, visit https://intercept.typo3.com/admin/docs/deployments and check “Recent actions” (scroll down). The repository should have created a “Docs hook ping from github repository”.

Bitbucket Cloud

Add auto rendering for a repository via Bitbucket webhook in five steps:

  1. Go to “Settings” section within the repository

  2. Go to “Webhooks” section within the repository settings

  3. Add webhook

  4. Fill in webhook configuration

    1. Choose a title for this hook: e.g. “TYPO3 Docs”.
    2. Fill URL field with https://docs-hook.typo3.org .
    3. Enable “Active” Status.
    4. Select Repository push for “Triggers”.
    5. Click on “Save”
  5. Webhook was added

    Bitbucket should show a notice, which disappears after some seconds, that creation of webhook was successful. Also the webhook should be shown in the list.

  6. (Optional) visit intercept and check request

    If curious, visit https://intercept.typo3.com/admin/docs/deployments and check “Recent actions” (scroll down).

    In order to appear, the hook needs to be triggered. Therefore either the branch master can be pushed. Or a new Branch documentation-draft can be created and pushed.

GitLab Cloud and GitLab self-hosted

Add auto rendering for a repository via GitLab webhook in four steps:

  1. Go to “Integrations” section within the repository

  2. Add webhook by filling in webhook configuration

    1. Fill URL field with https://docs-hook.typo3.org .
    2. Select Push events and Tag push events for “Trigger”.
    3. Click on “Add webhook”
  3. Webhook was added

    The webhook should be shown in the list (scroll down).

  4. (Optional) Trigger webhook and visit intercept to check request

    If curious, visit https://intercept.typo3.com/admin/docs/deployments and check “Recent actions” (scroll down).

    In order to appear, the hook needs to be triggered. Therefore either the branch master can be pushed. Or a new Branch documentation-draft can be created and pushed.