Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This branch was successfully deployed
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.
Six legacy customization URLs reported as 404s in Search Console have existing replacements but no configured aliases. Add those exact mappings to Mintlify redirects, with permanent redirects explicitly enabled. The redirect schema, unique-source and target-file checks pass, and all six hosted preview requests return 308 then 200 at the intended destinations; Mintlify drops query strings. Full local Mintlify validation fails on the same pre-existing supported-models.mdx:62 parsing error on main, while the hosted deployment and GitHub checks pass. No SDK runtime or API behavior changes; rollback removes these six entries, though clients may cache permanent redirects.