commit-status-updater
commit-status-updater copied to clipboard
fix: Use Node 20
fixes #528
@akatov: Invalid title for the PR, the title needs to be like:
-
refactor: this is a refactor commit
=> if using semantic-release will trigger a patch release -
fix: this is a fix commit
=> if using semantic-release will trigger a patch release -
feat: this is a feature commit
=> if using semantic-release will trigger a minor release -
major: this is a major commit
=> if using semantic-release will trigger a major release -
doc: this is a doc commit
=> if using semantic-release won't trigger a new release -
build: this is a build commit
=> if using semantic-release will trigger a patch release -
no-release: this is a no-release commit
=> won't trigger a new release
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: akatov
Once this PR has been reviewed and has the lgtm label, please assign alexouzounis for approval by writing /assign @alexouzounis
in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment
Welcome @akatov! It looks like this is your first PR to ouzi-dev/commit-status-updater 🎉
Hi @akatov. Thanks for your PR.
I'm waiting for a ouzi-dev member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
What needs to happen to get this PR landed?
/approve
/ok-to-test
@akatov: The following tests failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
validate-no-creds | a9e988ec5454692ff7745a509452422a35172ad6 | link | true | validate-no-creds |
validate-prow-yaml | a9e988ec5454692ff7745a509452422a35172ad6 | link | true | validate-prow-yaml |
Full PR test history. Your PR dashboard.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
Hi @akatov, first sorry for the delay with the PR. Looks like our Prow is not happy right now 😞 , so let me check what is happening and I'll try to merge this as soon as possible!
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: akatov, belitre
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [belitre]
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment
This pull request is included in version 2.0.2