Skip to content

Conversation

florent-leborgne
Copy link

^^

@florent-leborgne florent-leborgne requested a review from a team as a code owner March 7, 2025 10:56
Copy link

github-actions bot commented Mar 7, 2025

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.

Copy link
Contributor

mergify bot commented Mar 7, 2025

This pull request is now in conflict. Could you fix it @florent-leborgne? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch <remote-repo>
git checkout -b rns-900rc1-kibana <remote-repo>/rns-900rc1-kibana
git merge <remote-repo>/9.0
git push <remote-repo> rns-900rc1-kibana

@lcawl
Copy link
Contributor

lcawl commented Mar 7, 2025

This PR was affected by #2984 so I've pushed a commit to fix the conflicts. Basically the rc1 content is in a separate source file but get published in a single page alongside the other kibana 9.0 releases.

@lcawl lcawl force-pushed the rns-900rc1-kibana branch from b5f4f42 to d471b3c Compare March 7, 2025 18:05
@wajihaparvez
Copy link

Thank you! LGTM with two small comments 🚀

@florent-leborgne florent-leborgne merged commit 26426b0 into elastic:9.0 Mar 12, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants