Add redirect for moved page
What does this MR do?
This MR adds a redirect stub from doc/user/project/integrations/mlflow_client.md
to its new location, doc/user/project/ml/experiment_tracking/mlflow_client.md
.
I noticed that the hourly deployment pipeline https://gitlab.com/gitlab-org/gitlab-docs/-/pipelines/929001158/failures failed, and all the errors were pointing to user/project/integrations/mlflow_client.html
being missing. I remembered @eduardobonet had posted a review request in #tw-team a few hours ago, and had a hunch the two were related because of the file name.
Assigning to @sselhorn and @lciutacu because of the content of !126140 (merged). It's possible that more edits are needed to that page; feel free to repurpose this MR in whatever ways you see fit.
Related issues
- Related to Improves docs for Model experiment tracking (!126140 - merged) where the file was moved
- Related to Fix destination of MLflow client page (gitlab-docs!4061 - merged) which fixes the left nav
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding or changing the main heading of the page (H1), ensure that the product tier badge is added. -
If you are a GitLab team member, request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
If you are a GitLab team member and only adding documentation, do not add any of the following labels:
~"frontend"
~"backend"
~"type::bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
Reviewer's checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. - Technical writer review items:
-
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. -
Ensure a release milestone is set. - If relevant to this MR, ensure content topic type principles are in use, including:
-
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. - If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.