github-action: support check/lint/pre-commit

[v1v]

Proposed commit message

• WHAT: github-action: support check/lint/pre-commit.
• WHY: remove support in Jenkins for low-hanging fruit. It was partially done in the past in action: run check, check-default and pre-commit #32723

Further actions

• Update branch-protection:
  • Add pre-commit / pre-commit

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @v1v? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Duration: 131 min 34 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[v1v]

There is no need to support this

[v1v]

For some reason these checks were not migrated in #32723

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 45c430d

History

• 💚 Build #2984 succeeded 7a8d2f3
• 💚 Build #2981 succeeded 5df2fe0
• 💚 Build #2977 succeeded b502de3
• 💚 Build #2976 succeeded e2b8d36

cc @v1v

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 45c430d

History

• 💚 Build #1770 succeeded 7a8d2f3
• 💚 Build #1767 succeeded 5df2fe0
• 💚 Build #1763 succeeded b502de3
• 💚 Build #1762 succeeded e2b8d36

cc @v1v

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 45c430d

History

• 💚 Build #1777 succeeded 7a8d2f3
• 💚 Build #1774 succeeded 5df2fe0
• 💚 Build #1770 succeeded b502de3
• 💚 Build #1769 succeeded e2b8d36

cc @v1v

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 45c430d

History

• 💚 Build #933 succeeded 7a8d2f3
• 💚 Build #930 succeeded 5df2fe0
• 💚 Build #926 succeeded b502de3
• 💚 Build #925 succeeded e2b8d36

cc @v1v

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: 45c430d

Failed CI Steps

• :linux: Unit Tests / family/core-rhel-9
• :windows: Unit Tests / family/core-windows-2016
• :windows: Unit Tests / family/core-windows-2022

History

• 💚 Build #2066 succeeded 7a8d2f3
• 💚 Build #2063 succeeded 5df2fe0

cc @v1v

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: 45c430d

Failed CI Steps

• :windows:-family/core-windows-2016 Unit Tests
• :windows:-family/core-windows-2022 Unit Tests

History

• 💚 Build #3406 succeeded 7a8d2f3

cc @v1v

[dliappis]

LGTM

[v1v]

I don't know who has the superpower to merge, but! It will require a couple of further changes afterwards, as noted in the description.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
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 upstream
git checkout -b feature/check-on-gh-actions upstream/feature/check-on-gh-actions
git merge upstream/main
git push upstream feature/check-on-gh-actions

[alexsapran]

Since we are moving to BK, I would like to ask if we can split this PR into two smaller ones, one containing only the changes to the .pre-commit-config.yaml and then a follow-up to either try adding it to BK or, if that fails then the GH workflow.