Skip to content

[8.15] Update llm-performance-matrix.asciidoc (backport #6787) #6792

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

Open
wants to merge 1 commit into
base: 8.15
Choose a base branch
from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 25, 2025

8.x component of docs-content/issues/1206

Preview


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

(cherry picked from commit ac6ee71)

# Conflicts:
#	docs/AI-for-security/llm-performance-matrix.asciidoc
@mergify mergify bot requested a review from a team as a code owner April 25, 2025 20:49
Copy link
Contributor Author

mergify bot commented Apr 25, 2025

Cherry-pick of ac6ee71 has failed:

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

You are currently cherry-picking commit ac6ee710.
  (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/AI-for-security/llm-performance-matrix.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.

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