-
Notifications
You must be signed in to change notification settings - Fork 352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix broken links in documentation #6305
Conversation
🎊 PR Preview bb00c91 has been successfully built and deployed to https://treeverse-lakeFS-preview-pr-6305.surge.sh 🕐 Build time: 0.014s 🤖 By surge-preview |
7b87ab4
to
b6fc43a
Compare
That one understands `.md` suffixes, and is arguably nicer to use. Absolute links in aws.md
851c104
to
e52dbce
Compare
Hiyush reviewers...How to reviewSorry for the too-large PR. Unfortunately #6294 is the tip of the iceberg (and I don't mean the table format). Many of our links were broken, for multiple reasons. The main change is to change the instructions for how to link -- please start by reviewing that one! After that, many links were simply broken -- not only the ones referenced in the issue. I don't know why our "check links" check failed to find them; the fact of the matter is that it did not. Additionally, many of our anchored links were also broken; I fixed all of those that I could find. What to reviewMost of the changes follow one of these three mechanics:
I did not fix any link names in (non-Markdown...) assets. There is no risk of breakage there: no anchors, no extensions change. I believe that changing these would increase risk of breakage. Some of the changes reflect broken links that the Jekyll Why botherThe existing docs contain multiple breakages, and it seems that the Surge-based link checking was unable to find them. It does find other breakages, that Jekyll does not find, so best to keep both. |
.github/workflows/docs-pr.yaml
Outdated
@@ -6,6 +6,9 @@ on: | |||
- "docs/**" | |||
branches: | |||
- master | |||
push: | |||
paths: | |||
- "docs/**" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we do. So I'll move it to another PR and ask you and @nopcoder to TAL.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed this, opened #6311.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Marvelous!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
!
.github/workflows/docs-pr.yaml
Outdated
@@ -6,6 +6,9 @@ on: | |||
- "docs/**" | |||
branches: | |||
- master | |||
push: | |||
paths: | |||
- "docs/**" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we do. So I'll move it to another PR and ask you and @nopcoder to TAL.
The `.md` -> `.html` translation doesn't appear to work with `#` anchors. But... if we use an unsuffixed page name then _no_ translation is needed, and it might work!
It seems from [Jekyll docs](https://jekyllrb.com/docs/liquid/tags/#linking-to-posts) that there is no way to add anchors to link tags _inside_ a Markdown link. Instead, use references at the end of the file, where they seem to work.
Don't bother with images and other assets, though -- they are actually _easier_ to map because their extensions never change etc.
reference/{authorization => rbac}
Uggh.
38c25f3
to
bb00c91
Compare
This makes Surge try harder and run more often. Discovered while I was working on #6305, where it ran once after creating the PR but then stopped. Admittedly GitHub was not particularly responsive to running actions at the time.
THANKS! |
Also make them relative, which relies less on Jekyll-time magic and
therefore easier to check while working locally.
Fixes #6294.