Skip to content
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

Update component readiness test mapping #169

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

openshift-trt
Copy link
Contributor

Automatically generated component mapping update

@openshift-ci openshift-ci bot requested review from deads2k and deepsm007 December 18, 2024 04:02
Copy link
Contributor

openshift-ci bot commented Dec 18, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-trt

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Dec 18, 2024
Copy link
Contributor

openshift-ci bot commented Dec 18, 2024

Hi @openshift-trt. Thanks for your PR.

I'm waiting for a openshift-eng 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-sigs/prow repository.

@openshift-trt openshift-trt force-pushed the update branch 8 times, most recently from 54a086c to bce7ea2 Compare December 26, 2024 04:02
@openshift-trt openshift-trt force-pushed the update branch 7 times, most recently from 457c6cc to 530aa89 Compare January 2, 2025 04:02
@openshift-trt openshift-trt force-pushed the update branch 7 times, most recently from acecd58 to 8bf1d6f Compare January 9, 2025 04:02
@openshift-trt openshift-trt bot force-pushed the update branch 2 times, most recently from 5099e8e to 190caab Compare January 11, 2025 04:02
@openshift-trt openshift-trt bot force-pushed the update branch 8 times, most recently from 1efb276 to 68b83ab Compare January 19, 2025 04:02
@openshift-trt openshift-trt bot force-pushed the update branch 4 times, most recently from 3930314 to 6dad32a Compare January 23, 2025 04:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant