-
Notifications
You must be signed in to change notification settings - Fork 1.6k
🌱 (ci) - Fix the job to check the PR title and no longer use deprecated github action #4095
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
🌱 (ci) - Fix the job to check the PR title and no longer use deprecated github action #4095
Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: camilamacedo86 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
db4dec7 to
4979e43
Compare
3aedb22 to
20bd56b
Compare
7723e0a to
8b4487e
Compare
|
Hi @sbueringer We need to deprecate it in the kubebuilder tools repo I will move with this one to fix our CI |
8b4487e to
e208821
Compare
|
New changes are detected. LGTM label has been removed. |
…ed github action (kubernetes-sigs#4095) The kubebuilder-release-tools project is no longer really maintained. The image required for checks is deprecated due the infrastructure used to build and promote it be deprecated. Given the minimal nature of the check, it's unnecessary to maintain a GitHub Action for this purpose. Also, it broke 1 day ago. Note that we need to pass permissions via GitHub Token, which is not very safe. This is another reason why we need to proceed with these changes.
…hecker (kubernetes-sigs#4097) ci: Normalize text-based emoji codes to actual emojis in PR title checker Follow up of: kubernetes-sigs#4095
The kubebuilder-release-tools project is no longer really maintained. The image required for checks is deprecated due
the infrastructure used to build and promote it be deprecated. Given the minimal nature of the check, it's unnecessary to maintain a GitHub Action for this purpose.
Also, it broke 1 day ago. Note that we need to pass permissions via GitHub Token, which is not very safe. This is another reason why we need to proceed with these changes.
When it fails:
When the check pass: