Skip to content

Conversation

leemthompo
Copy link
Contributor

Docs component of https://github.com/elastic/ml-team/issues/1320

Backport

How far back should we backport?

@leemthompo leemthompo added the backport-8.15 Automated backport with mergify label Sep 2, 2024
@leemthompo leemthompo self-assigned this Sep 2, 2024
@leemthompo leemthompo requested a review from a team as a code owner September 2, 2024 07:30
Copy link

github-actions bot commented Sep 2, 2024

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.

@leemthompo leemthompo merged commit 437db55 into main Sep 2, 2024
4 checks passed
mergify bot pushed a commit that referenced this pull request Sep 2, 2024
@leemthompo leemthompo deleted the leemthompo-patch-e5-warranty branch September 2, 2024 10:14
leemthompo added a commit that referenced this pull request Sep 2, 2024
(cherry picked from commit 437db55)

Co-authored-by: Liam Thompson <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-8.15 Automated backport with mergify

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants