Skip to content

docs(redirects): catch 7 stale flaky-tests + code-quality paths#216

Open
samgutentag wants to merge 2 commits into
mainfrom
sam-gutentag/redirect-failure-rate
Open

docs(redirects): catch 7 stale flaky-tests + code-quality paths#216
samgutentag wants to merge 2 commits into
mainfrom
sam-gutentag/redirect-failure-rate

Conversation

@samgutentag
Copy link
Copy Markdown
Member

@samgutentag samgutentag commented Jun 5, 2026

Adds redirects for paths that moved in the docs restructure and were still 404ing.

Redirects added

Old path (404) Destination (200)
/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-test

Why

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.io links (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-test row needs its own entry because Mintlify redirects are exact-match: the existing redirect on the parent /use-mcp-server/mcp-tool-reference doesn't catch the /fix-flaky-test leaf.

Verification

  • Site-relative destinations, matching the existing ~300 redirects entries in docs.json.
  • docs.json re-validated as well-formed JSON, no duplicate source keys.
  • All seven destinations confirmed 200 against live docs.

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) <noreply@anthropic.com>
@mintlify
Copy link
Copy Markdown
Contributor

mintlify Bot commented Jun 5, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
trunk 🟢 Ready View Preview Jun 5, 2026, 5:41 PM

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) <noreply@anthropic.com>
@samgutentag samgutentag changed the title docs(redirects): add /flaky-tests/detection/failure-rate redirect docs(redirects): catch 7 stale flaky-tests + code-quality paths Jun 5, 2026
Copy link
Copy Markdown
Member Author

Docs-PR Verify | 2026-06-06 | verdict: ✅ live

Signal Detail
Eng PR trunk2#4102 - OPEN (docs redirects are independent of app-side fix; all 7 destinations confirmed 200 on live docs)
LD flag none
Linear none

Redirect entries are pure docs-layer changes and are not gated on the app-side PR. Merge when ready.


Generated by Claude Code

@samgutentag samgutentag added the ready to merge Verify docs PR: customers can use this. Ready to publish. label Jun 6, 2026 — with Claude
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready to merge Verify docs PR: customers can use this. Ready to publish.

Development

Successfully merging this pull request may close these issues.

1 participant