Add redirects for 18 legacy doc paths still returning 404#694
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
71ff6e8 to
cbe8f84
Compare
The 'Check tooltip imports' required status check is path-filtered to **.mdx, so it never runs on json-only PRs and blocks the merge as 'expected'. Whitespace-only touch to one .mdx to make it run. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
@lavanya-gunreddi one more approval click needed, sorry. The merge was blocked by the required 'Check tooltip imports' status check: its workflow is path-filtered to .mdx files, so on this json-only PR it never ran and the merge sat waiting forever. I pushed a whitespace-only touch to one .mdx to trigger it (it passed in 9s), but that push reset your approval. No content changed since your review beyond that whitespace line. Once re-approved this merges immediately. Separately, worth fixing the root cause so this doesn't bite the next docs.json-only PR: either remove the paths filter from validate-tooltips.yml (the script is a 9-second no-op when nothing relevant changed) or drop it from the required checks list. |
What
GSC's 'Not found (404)' validation on the runpod.io domain property failed (July 3 email); a chunk of the still-404 URLs are legacy docs paths from old structures:
/graphql/*,/category/*,/docs/*, and pre-restructure serverless paths. Several carry external backlinks (/graphql/manage-podshas 11 referring pages).Change
Adds 18 entries to the
redirectsarray indocs.json, each mapped to the closest current page. All destination paths verified to exist (as .mdx or live 200). No content changes.After this deploys, re-request validation in GSC for the 'Not found (404)' issue.
🤖 Generated with Claude Code