Generate API docs from spec - #1831
Closed
github-actions[bot] wants to merge 0 commit into
Closed
github-actions[bot] wants to merge 0 commit into
github-actions[bot] wants to merge 0 commit into
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
github-actions
Bot
force-pushed
the
docs/automatic-api-docs-update
branch
from
September 18, 2026 13:02
175f4e5 to
d92fbda
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was automatically generated by the API docs synchronization action. Please review the changes and merge if they look good.
Note
Low Risk
Intended changes are generated API reference documentation only, with no runtime or security-sensitive code in scope.
Overview
No substantive file changes appear in the supplied diff (only an empty placeholder), so there is nothing concrete to review from the patch itself.
The PR metadata describes the usual automated API docs synchronization run: regenerating GitBook reference pages under
developer-tools/snyk-api/reference/from the OpenAPI specs viatools/api-docs-generator, along with the corresponding navigation entries. If the real branch contains updates, expect churn in generated endpoint docs (OpenAPI embed blocks and schemas), not hand-written product copy.Reviewed by Cursor Bugbot for commit d92fbda. Bugbot is set up for automated code reviews on this repo. Configure here.