Fix 404 links in .NET zero-code troubleshooting docs#9718
Merged
chalin merged 4 commits intoApr 22, 2026
Conversation
Agent-Logs-Url: https://github.com/open-telemetry/opentelemetry.io/sessions/ef07e673-a814-49e7-af50-290497c15f4e Co-authored-by: chalin <4140793+chalin@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix broken links in troubleshooting documentation
Fix 404 links in .NET zero-code troubleshooting docs
Apr 22, 2026
Contributor
|
/fix:refcache |
Contributor
|
✅ |
Merged
martincostello
approved these changes
Apr 22, 2026
chalin
approved these changes
Apr 22, 2026
Contributor
There was a problem hiding this comment.
Only link fixes by pinning failing GH URLs to the last hash at which the given resource was valid. Approving for all SIGs and locales.
Feedback is still welcome.
Thanks @martincostello for the approval.
/cc @vitorvasc
jaydeluca
approved these changes
Apr 22, 2026
Contributor
|
Thanks @jaydeluca for the review. |
Contributor
|
Btw, this is a patch PR over: |
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
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.
Three URLs in the .NET zero-code troubleshooting page point to files removed from
open-telemetry/opentelemetry-dotnet-instrumentationby PR #4783 (2026-03-30), which eliminated theDOTNET_ADDITIONAL_DEPS/DOTNET_SHARED_STOREmechanism.Changes
content/en/docs/zero-code/dotnet/troubleshooting.mdandcontent/fr/docs/zero-code/dotnet/troubleshooting.md: Replace threeblob/main/...links with pinned commit-SHA URLs pointing to the last commit at which each file existed:Directory.Build.props→ pinned toc27acd9AdditionalDeps/Directory.Packages.props→ pinned tof2d70bdnetfx_assembly_redirection.h→ pinned to62b4a6astatic/refcache.json: Remove the three404entries for the oldblob/main/...URLs so the link checker stops failing on them.Original prompt
Context
PR #9679 (branch
otelbot/refcache-refresh) is a refcache refresh PR, and its link-checking CI is failing because three URLs in thedocs/zero-code/dotnet/troubleshooting/page return HTTP 404.The three failing URLs all point to files that were removed from
open-telemetry/opentelemetry-dotnet-instrumentationon themainbranch by PR open-telemetry/opentelemetry-dotnet-instrumentation#4783 (commitad0c2dc720bab8d920de8bdbcef226596fd257b0, 2026-03-30), which eliminated theDOTNET_ADDITIONAL_DEPS/DOTNET_SHARED_STOREmechanism.Failing URLs and their replacements
The fix is to update each URL to pin to the last commit SHA at which the file still existed:
Directory.Build.propshttps://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/src/OpenTelemetry.AutoInstrumentation.AdditionalDeps/Directory.Build.propshttps://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/c27acd9bd0f82de47217fba660d9f979e0a0cc2d/src/OpenTelemetry.AutoInstrumentation.AdditionalDeps/Directory.Build.propsDirectory.Packages.props(AdditionalDeps)https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/src/OpenTelemetry.AutoInstrumentation.AdditionalDeps/Directory.Packages.propshttps://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/f2d70bd0f095852bf0270aad61b60dfe1ea7834f/src/OpenTelemetry.AutoInstrumentation.AdditionalDeps/Directory.Packages.propsnetfx_assembly_redirection.hhttps://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/src/OpenTelemetry.AutoInstrumentation.Native/netfx_assembly_redirection.hhttps://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/62b4a6a855608a925caeea95752167df5a0960a0/src/OpenTelemetry.AutoInstrumentation.Native/netfx_assembly_redirection.hFiles to edit
Update the URLs in both language versions of the troubleshooting page:
content/en/docs/zero-code/dotnet/troubleshooting.mdcontent/fr/docs/zero-code/dotnet/troubleshooting.md(Check for any other language versions under
content/*/docs/zero-code/dotnet/troubleshooting.mdthat contain these same links and update them too.)Refcache update
After updating the markdown sources, update
static/refcache.json:blob/main/...) if present.Acceptance criteria
docs/zero-code/dotnet/troubleshooting/are replaced with the pinned commit-SHA URLs listed above, in all language variants of the file.static/refcache.jsonno longer contains entries for the three failingblob/main/...URLs.htmltest/link-check CI job on the PR passes for these three URLs.Base branch
Target this patch at the existing PR branch
otelbot/refcache-refresh(PR #9679) so it lands in that PR.The following is the prior conversation context from the user's chat exploration (may be truncated):
User: Link checking is failing. From this log we see the 404s: