Our webhooks pipeline creates autogenerated webhooks documentation for docs.github.com/webhooks-and-events/webhooks/webhook-events-and-payloads from the OpenAPI stored in the open-source repository github/rest-api-description.

The pipeline is used to generate data that is used by the docs.github.com site when deployed locally, in preview environments, or in production.

A workflow is used to trigger the automation of the webhooks documentation. The workflow runs automatically on a schedule. The workflow that triggers the webhooks pipeline also triggers other automation pipelines that use the OpenAPI as the source data:

• GitHub Apps
• REST
• Webhooks

The workflow automatically creates a pull request with the changes (for all three pipelines) and the label github-openapi-bot.

The workflow runs the src/rest/scripts/update-files.js script, which then calls the src/webhooks/scripts/sync.js script.

To run the webhooks pipeline locally:

1. Clone the github/rest-api-description repository inside your local docs-internal repository.
2. Run src/rest/scripts/update-files.js -s rest-api-description -o webhooks.

• src/webhooks/data - The automatically generated data files created by running this pipeline.
• src/webhooks/lib - The source code used in production to display the webhook docs and configuration files edited by content and engineering team members.
  • src/webhooks/lib/config.json - A configuration file used to specify metadata about the webhooks pipeline.
• src/webhooks/scripts - The scripts and source code used run the webhooks pipeline, which updates the src/webhooks/data directory.
  • src/webhooks/scripts/sync.js - The entrypoint script that runs the webhooks pipeline.
• src/webhooks/tests - The tests used to verify the webhooks pipeline.

The src/webhooks/lib/config.json file can contain any metadata needed by the content and engineering teams to configure the webhooks pipeline. The file currently only contains the following property:

• sha - The SHA of the commit in github/rest-api-description that was used to generate the data in src/webhooks/data. This value is automatically updated when the pipeline runs.

The content writers can manually update frontmatter and introductory content in the associated Markdown file content/webhooks-and-events/webhooks/webhook-events-and-payloads. Automated content gets appended to the end of the file.

Slack: #docs-engineering Repo: github/docs-engineering

If you have a question about the webhooks pipeline, you can ask in the #docs-engineering Slack channel. If you notice a problem with the webhooks pipeline, you can open an issue in the github/docs-engineering repository.