Fix documentation redirects for removed getting-started pages#18789
Merged
Fix documentation redirects for removed getting-started pages#18789
Conversation
Co-authored-by: harupy <17039389+harupy@users.noreply.github.com>
Co-authored-by: harupy <17039389+harupy@users.noreply.github.com>
Contributor
|
@Copilot Thank you for the contribution! Could you fix the following issue(s)? ⚠ Invalid PR templateThis PR does not appear to have been filed using the MLflow PR template. Please copy the PR template from here and fill it out. |
Co-authored-by: harupy <17039389+harupy@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix documentation links and maintain old redirects
Fix documentation redirects for removed getting-started pages
Nov 12, 2025
Collaborator
WeichenXu123
left a comment
There was a problem hiding this comment.
LGTM except one comment
Co-authored-by: harupy <17039389+harupy@users.noreply.github.com>
Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
harupy
reviewed
Nov 12, 2025
Signed-off-by: Harutaka Kawamura <hkawamura0130@gmail.com>
- Remove unused createRedirectsWithPrefixes helper function - Add redirects for both /getting-started/* and /ml/getting-started/* paths - Ensures all removed pages from PR #18379 have proper redirects - Fixes build error caused by redirect conflicts Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
Contributor
|
Documentation preview for 43785cc is available at: More info
|
Tian-Sky-Lan
pushed a commit
to Tian-Sky-Lan/mlflow
that referenced
this pull request
Nov 24, 2025
…#18789) Signed-off-by: harupy <17039389+harupy@users.noreply.github.com> Signed-off-by: Harutaka Kawamura <hkawamura0130@gmail.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: harupy <17039389+harupy@users.noreply.github.com> Co-authored-by: Harutaka Kawamura <hkawamura0130@gmail.com> Signed-off-by: Tian Lan <sky.blue266000@gmail.com>
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.
Related Issues/PRs
Fixes redirects broken by #18379
What changes are proposed in this pull request?
PR #18379 removed getting-started tutorial pages but only added redirects for
/getting-started/*paths. The pages were also accessible via/ml/getting-started/*paths (because the classic-ml plugin usesrouteBasePath: 'ml'), which now return 404 errors.This PR adds the missing
/ml/*redirects so both path formats work correctly.How is this PR tested?
npm run buildsucceedsDoes this PR require documentation update?
Release Notes
Is this a user-facing change?
Fixes broken documentation redirects for getting-started tutorial pages that were returning 404 errors after recent restructuring.
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/docs: MLflow documentation pagesHow should the PR be classified in the release notes? Choose one:
rn/bug-fix- A user-facing bug fix worth mentioning in the release notesShould this PR be included in the next patch release?