Closed
Conversation
Contributor
Author
|
/ci |
Contributor
|
Pinging @elastic/kibana-docs (Team:Docs) |
Contributor
|
🤖 Jobs for this PR can be triggered through checkboxes. 🚧
ℹ️ To trigger the CI, please tick the checkbox below 👇
|
Contributor
💔 Build Failed
Failed CI StepsHistory
|
kilfoyle
approved these changes
Apr 8, 2025
Contributor
kilfoyle
left a comment
There was a problem hiding this comment.
LGTM! 🚢
Still in draft mode but I trust it's okay to approve.
Contributor
Author
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.
Summary
This PR:
server.publicBaseUrlkeyword in the service and updatespublic_base_url.tsxto use it, since the hard-coded fragment will not work when we shift to the new docs site.This update is accomplished by taking our current (work in progress) list of redirects and using it to replace the values in
get_doc_links.tsvia a python script. It does not check the validity of the existing anchors in the URLs.Refer to #215084 (comment) for discussion about the build failures.
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesIdentify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.