| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
parent directory.. | ||||
Our GitHub Apps pipeline creates autogenerated documentation for docs.github.com 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 GitHub Apps documentation. The workflow runs automatically on a schedule. The workflow that triggers the GitHub Apps pipeline also triggers other automation pipelines that use the OpenAPI as the source data:
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.
To run the GitHub Apps pipeline locally:
The src/github-apps/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:
The content writers can manually update parts of the autogenerated Markdown file content/rest/overview/endpoints-available-for-github-apps.md. All frontmatter properties except versions can be manually modified and will not be overwritten on subsequent runs of the pipeline. The pipeline does update the versions property on each run.
Writers can also add an introduction paragraph above the following Markdown comment:
<!-- Content after this section is automatically generated -->Slack: #docs-engineering Repo: github/docs-engineering
If you have a question about the GitHub Apps pipeline, you can ask in the #docs-engineering Slack channel. If you notice a problem with the GitHub Apps pipeline, you can open an issue in the github/docs-engineering repository.
| Back | FazBrowse Home | New Git URL |