docs(redirects): catch 7 stale flaky-tests + code-quality paths#216
Open
samgutentag wants to merge 2 commits into
Open
docs(redirects): catch 7 stale flaky-tests + code-quality paths#216samgutentag wants to merge 2 commits into
samgutentag wants to merge 2 commits into
Conversation
Redirect the old /flaky-tests/detection/failure-rate path to the current failure-rate-monitor page. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
These paths moved in the docs restructure and were still being linked from the trunk2 web app (fixed in trunk2#4102). Catch them at the docs layer so external links, bookmarks, and cached app builds don't 404. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
samgutentag
changed the title
Member
Author
|
Docs-PR Verify | 2026-06-06 | verdict: ✅ live
Redirect entries are pure docs-layer changes and are not gated on the app-side PR. Merge when ready. Generated by Claude Code |
samgutentag
added
the
ready to merge
Claude
Member
Author
|
Docs PR Verdict — 2026-06-08
Next sweep: 2026-06-09 Generated by Claude Code |
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
1 participant
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.
Adds redirects for paths that moved in the docs restructure and were still 404ing.
Redirects added
/flaky-tests/detection/failure-rate/flaky-tests/detection/failure-rate-monitor/code-quality/linters/run-linters/code-quality/overview/linters/run-linters/code-quality/debugging/code-quality/overview/debugging/code-quality/linters/ignoring-issues-and-files/code-quality/overview/linters/ignoring-issues-and-files/flaky-tests/ci-providers/flaky-tests/get-started/ci-providers/flaky-tests/github-pull-request-comments/flaky-tests/management/github-pull-request-comments/flaky-tests/use-mcp-server/mcp-tool-reference/fix-flaky-test/flaky-tests/reference/mcp-reference/fix-flaky-testWhy
The first row is the path a 404 monitor flagged. The other six were found by sweeping the trunk2 web app for stale
docs.trunk.iolinks (app-side fix: trunk-io/trunk2#4102). Catching them at the docs layer also covers external links, bookmarks, and cached app builds during rollout — not just the app.The
fix-flaky-testrow needs its own entry because Mintlify redirects are exact-match: the existing redirect on the parent/use-mcp-server/mcp-tool-referencedoesn't catch the/fix-flaky-testleaf.Verification
redirectsentries indocs.json.docs.jsonre-validated as well-formed JSON, no duplicatesourcekeys.