Fix two links that 404 on code.visualstudio.com - #10120
Open
Hüseyin Kutsi Balcı (kutsibalci) wants to merge 2 commits into
Open
Fix two links that 404 on code.visualstudio.com#10120Hüseyin Kutsi Balcı (kutsibalci) wants to merge 2 commits into
Hüseyin Kutsi Balcı (kutsibalci) wants to merge 2 commits into
Conversation
A stray slash before the anchor in rust.md, and a Microsoft Learn path written as a site-relative link in finetune.md.
Nick Trogh (ntrogh)
enabled auto-merge (squash)
August 10, 2026 09:35
Contributor
Author
|
@microsoft-github-policy-service agree |
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
2 participants
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.
What
Two links in published topics that return 404 on code.visualstudio.com.
+2/-2, two files.docs/languages/rust.md:266/docs/debugtest/debugging.md/#launch-configurations/docs/debugtest/debugging.md#launch-configurationsdocs/intelligentapps/finetune.md:399/uwp/api/windows.applicationmodel.limitedaccessfeatureshttps://learn.microsoft.com/uwp/api/...Verified against the live site, not the Markdown
Per the note at the top of CONTRIBUTING.md, I resolved every candidate against the production site rather than trusting my reading of the source. Both of these are
404there today; the fixed forms are200.That check is what removed most of the sweep. Of 577 distinct site-relative link targets, 69 had no matching file in the repository, but only 11 actually fail on the site —
/updates/v1_74.mdis served fromrelease-notes/,/api/references/vscode-apiis generated,/assets/**comes from a separate pipeline, and a dozen more resolve throughredirection.jsonor a site-level redirect (/docs/getstarted/keybindings.md→/docs/configure/keybindings,/docs/azure/docker.md→/docs/containers/overview, and so on). Those all work and are untouched here.Why each is an anomaly rather than a convention
The stray slash.
.md/#anchoroccurs exactly once in the repository. The correct.md#anchorform occurs 840 times.The Microsoft Learn path.
docs/intelligentapps/finetune.mdlinks to theLimitedAccessFeaturesclass with a site-relative/uwp/...path, which the site resolves againstcode.visualstudio.comand cannot find. Every other Microsoft Learn reference in this repository — 394 of them — is written as a fullhttps://learn.microsoft.com/...URL. This is the only one that is not. The target itself is fine:https://learn.microsoft.com/uwp/api/windows.applicationmodel.limitedaccessfeaturesreturns200.Deliberately left alone
/issuesand eight/Issues/Detail/NNNNNlinks. They 404, but they are inrelease-notes/v0_3_0.mdthroughv0_8_0.md— a dated record of releases from 2015, pointing at an issue tracker that no longer exists. Rewriting history seemed wrong; happy to include them if you would rather they were fixed./docs/copilot/getting-started.md, which 404s but appears only in.github/skills/, not in published content.AI disclosure
AI-assisted (Claude Code). The tool ran the link sweep and the live verification and drafted this description. I checked the findings before opening: each surviving link was requested against code.visualstudio.com, the replacement URLs were requested too, and the two anomaly counts above were measured across the repository. I have reviewed and understood the change and take responsibility for it.