Skip to content

docs: fix broken source-file links in managed chaining intro - #2579

Merged
Perksey merged 2 commits into
dotnet:mainfrom
mokashang:docs/fix-managed-chaining-links
Jul 26, 2026
Merged

docs: fix broken source-file links in managed chaining intro#2579
Perksey merged 2 commits into
dotnet:mainfrom
mokashang:docs/fix-managed-chaining-links

Conversation

@mokashang

@mokashangmokashang commented May 12, 2026

Copy link
Copy Markdown
Contributor

Summary of the PR

Fixes the three broken links in the opening paragraph of the Managed Chaining docs page (documentation/vulkan/structure-chaining/managed-chaining.md).

The links used repo-relative paths (../../src/Vulkan/...). On the rendered docs site they get rewritten to /Silk.NET/docs/src/..., which doesn't exist, so all three 404. Two of the targets were also renamed during the 3.0 work — Chain.gen.tt is now Chain.g.tt, and Chain.gen.cs is now Chain.g.cs.

Switched the three links to absolute GitHub URLs pointing at the current paths on main:

  • Chain.cs — same file
  • Chain.gen.ttChain.g.tt
  • Chain.gen.csChain.g.cs

All three new URLs return HTTP 200.

Related issues, Discord discussions, or proposals

Fixes the three links initially called out by #2566

Further Comments

Scope is intentionally limited to the three links called out in the issue (the opening paragraph). No other links in the file were changed. The unrelated CRLF normalization on (WIP) Proposal - Axis Input Devices.md that git status shows on a fresh clone is not included in this PR.

The opening paragraph of `documentation/vulkan/structure-chaining/managed-chaining.md`
linked to source files via repo-relative paths (e.g. `../../src/Vulkan/...`).
On the rendered docs site these resolve to `/Silk.NET/docs/src/...`, which
does not exist, so all three links 404.
Two of the targets were also renamed during 3.0 work: `Chain.gen.tt` is now
`Chain.g.tt`, and `Chain.gen.cs` is now `Chain.g.cs`.
Switch the three links to absolute GitHub URLs pointing at the current
file paths on `main`.
Fixesdotnet#2566

@ExaniteExanite left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. I'll ping another maintainer to review it tomorrow and get this merged.

I also investigated a bit on my end and it looks like this is the correct way to go about it. Using relative links is messy considering how the website is built (I believe it's built from the 3.0 branch) and apparently leads to the file being downloaded instead, which isn't great.

@mokashang

mokashang commented May 12, 2026 via email

Copy link
Copy Markdown
ContributorAuthor

@Exanite
Exanite enabled auto-merge (squash) May 12, 2026 22:38
@Exanite
Exanite disabled auto-merge May 17, 2026 06:42
@Perksey
Perksey merged commit bfc3d35 into dotnet:mainJul 26, 2026
3 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants

@mokashang@Beyley@Exanite@Perksey