Make style of anchors consistent across docs #17442
Merged
Conversation
This file contains 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
jhlodin
requested review from
m57lyra and
mosabua
and removed request for
mosabua
|
Please squash the two commits @michaeleby1 |
Make style of ref links consistent across docs
michaeleby1
force-pushed
the
me/standardize-ref-anchors
branch
from
3e89e53 to
71f9cbe
Compare
Done |
|
Verified build locally. All good to go |
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.
Description
All anchors in Trino docs should be written with hyphens
.. _name-of-ref:, however some older anchors use underscores.. _name_of_ref:624 anchors use hyphens and 214 anchors use underscores
This PR changes those underscores to hyphens
The
:ref:links must also be changed to point to the anchors983
:ref:links use hyphens and 351:ref:links use underschorsThis PR changes those underscores to hyphens
I tested the build locally to ensure there were no issues
Additional context and related issues
Release notes
(x) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text: