-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
github-action: support check/lint/pre-commit #38175
Conversation
use github actions instead
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
|
||
- repo: https://github.com/elastic/apm-pipeline-library.git |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no need to support this
deploy/kubernetes/Jenkinsfile.yml
Outdated
@@ -12,11 +12,6 @@ when: | |||
tags: true ## for all the tags | |||
platform: "immutable && ubuntu-22" ## default label for all the stages | |||
stages: | |||
checks: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For some reason these checks were not migrated in #32723
💚 Build Succeeded
History
cc @v1v |
💚 Build Succeeded
History
cc @v1v |
💚 Build Succeeded
History
cc @v1v |
💚 Build Succeeded
History
cc @v1v |
💔 Build Failed
Failed CI StepsHistory
cc @v1v |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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. |
This pull request is now in conflicts. Could you fix it? 🙏
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
LGTM |
(cherry picked from commit bef2cc6) # Conflicts: # .pre-commit-config.yaml
(cherry picked from commit bef2cc6) # Conflicts: # .pre-commit-config.yaml
(cherry picked from commit bef2cc6)
Proposed commit message
Further actions
pre-commit / pre-commit
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs