fix fragment links for batch-spec-yaml-reference#1063
Merged
MaedahBatool merged 4 commits intoMay 8, 2025
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
MaedahBatool
approved these changes
May 8, 2025
Contributor
MaedahBatool
left a comment
There was a problem hiding this comment.
Fixed the merge conflicts. Let's make it live.
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.
Links to fragments (bookmarks) in
batch-spec-yaml-referencewere incorrect: they contained dashes where dots are in the headings, but the bookmark generator (GithubSlugger) creates ids by removing alpha-numeric characters and encoding spaces as dashes, so the links with dashes where there were dots didn't work.Remove all dashes; spot test the links.
Also did some general fixup of
batch-spec-yaml-referencelinks, where the dashes were underscores, and fixed a redirector that was directing to the wrong location.Tacked on a similar fix in
docs/admin/code_hosts/bitbucket_server.mdx