Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

Pinging @elastic/fleet (Team:Fleet)

buildkite build this

@elasticmachine run elasticsearch-ci/docs

@kpollich after running : node scripts/i18n_check.js --fix, there were no changes in the translation files

@PopoPilote90 I just pushed up d922ea8 to fix the lint error reported by CI.

In the future, file PR's from a branch on your fork - not the main branch of your fork. This will make things a little easier, and will allow CI to auto-commit lint failures like this instead of erroring as we did here:

[PopoPilote90/main ae741637f828] [CI] Auto-commit changed files from 'node scripts/eslint --no-cache --fix'
--
  | 1 file changed, 14 insertions(+), 15 deletions(-)
  | fatal: The upstream branch of your current branch does not match
  | the name of your current branch.  To push to the upstream branch
  | on the remote, use
  |  
  | git push https://github.com/PopoPilote90/kibana.git HEAD:main
  |  
  | To push to the branch of the same name on the remote, use
  |  
  | git push https://github.com/PopoPilote90/kibana.git HEAD
  |  
  | To choose either option permanently, see push.default in 'git help config'.

I'd also recommend setting up ESLint in your editor of choice to catch lint error likes this during development if possible. We typically recommend VS Code for development on Kibana, and run the ESLint extension.

@elasticmachine run elasticsearch-ci/docs

buildkite test this

💚 Build Succeeded

• Buildkite Build
• Commit: d922ea8
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

History

• 💔 Build #44048 failed 2dafa2b

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @kpollich