Repository navigation
fix: validate feedback examples against schemas and repair docs CI - #1
Merged
Merged
Conversation
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.
Replace the invalid inline Markdown config input with a checked-in config file, repair formatting and broken fragments, and correct outdated repository links. Add actual schema/example validation with format checking rather than JSON parsing alone.
Validation
Markdown lint passed; all 3 schema/example pairs validated; JavaScript and Python SDK syntax checks passed. Hosted API endpoints were not exercised.
Scope
Organisation-owned public repository only. Changes are proposed on a focused branch; no default-branch push or deployment.