Skip to content

Fix broken links - #317

Merged
TylerJang27 merged 3 commits into
mainfrom
mintlify/43dd70e4
Sep 15, 2026
Merged

TylerJang27 merged 3 commits into
mainfrom
mintlify/43dd70e4

Conversation

@mintlify

@mintlify mintlify Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Summary

mint broken-links and mint validate passed, but a deeper anchor audit found ~70 links pointing at anchors that no longer exist (mostly GitBook-style #id-N.-… anchors left over from migration, plus renamed headings and dead footnote refs). All are fixed and re-validated. A follow-up pass after the test collections launch (#330) fixed one more inbound link broken by the dashboard rewrite.

Changes

  • GitBook-style #id-N.-… anchors rewritten to Mintlify slugs (e.g. #id-2.-customize-your-transformation#2-customize-your-transformation) in flaky-tests/webhooks/*, flaky-tests/recipes/alert-on-test-escalation.mdx, and flaky-tests/reference/cli-reference.mdx.
  • 26 framework pages: otherci#id-1.-store-a-trunk_token-secret-in-your-ci-systemotherci#trunk-organization-slug-and-token (old heading no longer exists). Re-applied on top of the test collections rewrite of these pages after merging main.
  • Renamed/removed headings retargeted:
    • detection#stable-branchesdetection#branch-aware-detection (Bamboo, Cloud Build)
    • failure-rate-monitor#branch-pattern-syntax#branch-scope (pattern syntax lives under Branch Scope)
    • linear-integration#api-token-permissions#api-key-permissions
    • managing-your-organization#slug#organization-slug-and-token
    • billing#free-plans-and-trials#free-plan
    • quarantining#whats-affected#what-does-quarantined-mean; #using-the-trunk-cli-directly#updates-in-ci
    • get-started#id-4.-confirm-your-configuration…#step-3-verify-integration
    • github-integration#uploading-results / #what-is-a-.trunk-repository#what-is-a-trunk-repository
    • webhooks#testcaseinvestigationcompleted#test_case-investigation_completed
    • merge-queue/getting-started#submit-pull-requests/merge-queue/using-the-queue/reference#submitting-and-cancelling-pull-requests
    • lint config: #commands#run, #how-code-qualit-runs-linters#how-code-quality-runs-linters, output-parsing#node/#python../runtimes, run-linters#sample#recipes, ansible-lint ../#trigger-rules../configure-linters#trigger-rules
  • API anchors now point at the generated endpoint pages: merge#post-getmergequeuetestingdetailsmerge/get-details-about-testing-that-merge-queue-is-performing, merge#post-submitpullrequestmerge/submit-a-pull-request-to-a-merge-queue, api-reference#post-flaky-tests-link-ticket-to-test-caseapi-reference/link-a-ticket-to-a-test-case.
  • Dead footnote refs in billing.mdx (#user-content-fn-1, footnote never rendered) inlined as plain text; orphan footnote definition removed.
  • parallel-queues pages: dead merge-queue#single-mode-vs.-parallel-mode anchor → /merge-queue/optimizations/parallel-queues.
  • advanced-settings.mdx: dropped dead #custom-merge-commit-titles anchor (section only exists on the linking page itself); link now targets the Submit and cancel pull requests page.

Follow-up: test collections launch (#330)

  • Merged latest main (test collections pages published; framework pages rewritten). Conflicts resolved by keeping main's new collection-ID wording while re-applying the otherci anchor fix.
  • changelog/2026-04-15-flaky-tests-repositories-overview-dashboard.mdx: dashboard#repositories-overviewdashboard#repositories — the dashboard rewrite replaced the Repositories overview heading with a Repositories legacy-view section under Collections overview.

Context

Anchor slugs were verified against the rendered site (Mintlify converts . and other punctuation to -, keeps underscores). mint validate and mint broken-links both pass.

@mintlify

mintlify Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor Author

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

Project Status Preview Updated
trunk 🟢 Ready View Preview Sep 15, 2026, 7:41 PM

@trunk-io

trunk-io Bot commented Sep 9, 2026

Copy link
Copy Markdown

Merging to main in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

@TylerJang27
TylerJang27 merged commit ae7c813 into main Sep 15, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant