TOC nav for GraphQL changelog is broken

[mootari]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/graphql/overview/changelog

What part(s) of the article would you like to see updated?

All entries in the right-hand TOC navigation point to non-existing anchors.

Example:

• TOC anchor: #schema-changes-for-2025-11-06
• Actual anchor: #schema-changes-for-2025-11-06-3

Additional information

No response

[welcome]

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[Sharra-writes]

@mootari Thanks for pointing this out! A lot of the GraphQL documentation is auto-generated, so we'll have to fix this internally. I'll get this transferred over shortly.

[mootari]

@Sharra-writes I'm not sure that's true. It seems to me that it might suffice to pass an explicit slug prop in

docs/src/graphql/components/Changelog.tsx

Line 18 in 3160875

<HeadingLink as="h2">{heading}</HeadingLink>

[Sharra-writes]

@mootari I'll make note of that, but open source contributors usually can't alter files that aren't in the content and data folders in this repository. The CI checks are set to fail for all but a relatively narrow subset of files, since the documentation is open source but the files that build the site are not.

You can try and open a PR for it if you want to, to see if that particular file is allowed by some fluke, but there's a good chance it isn't.

[Nicksisw]

27122543 ในวันที่ อ. 11 พ.ย. 2025 05:53 Fabian Iwand ***@***.***> เขียนว่า:

…

*mootari* left a comment (github/docs#41185) <#41185 (comment)> @Sharra-writes <https://github.com/Sharra-writes> I'm not sure that's true. It seems to me that it might suffice to pass an explicit slug prop in https://github.com/github/docs/blob/3160875d4c57507e27cb3b76ebd855d8eaa5a576/src/graphql/components/Changelog.tsx#L18 — Reply to this email directly, view it on GitHub <#41185 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A53LEDZOIGHO6WFRW7ZISXT34EJNBAVCNFSM6AAAAACLSMNBXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMJUGIZDOMJZGE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[mootari]

You can try and open a PR for it if you want to

No, I believe you, I just wasn't aware of that particular context 🙂

[Sharra-writes]

@mootari We've alerted our engineers and opened an internal issue, so I'm going to close this one. Thanks again for bringing it to our attention!