Skip to content
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

[8.4] [DOCS] Removes frozen indices limitation item from anomaly detection docs (backport #2828) #2841

Closed
wants to merge 7 commits into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 10, 2024

Overview

This PR removes a anomaly detection limitation item about frozen indices that no longer applies from docs.


This is an automatic backport of pull request #2828 done by Mergify.

…docs. (#2828)

(cherry picked from commit 04632d2)

# Conflicts:
#	docs/en/stack/ml/anomaly-detection/ml-limitations.asciidoc
Copy link
Contributor Author

mergify bot commented Oct 10, 2024

Cherry-pick of 04632d2 has failed:

On branch mergify/bp/8.4/pr-2828
Your branch is up to date with 'origin/8.4'.

You are currently cherry-picking commit 04632d2f.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   docs/en/stack/ml/anomaly-detection/ml-limitations.asciidoc

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@szabosteve szabosteve closed this Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant