Skip to content

NO-JIRA: Update OWNERS_ALIASES#28

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
pierreprinetti:patch-1
Mar 26, 2026
Merged

NO-JIRA: Update OWNERS_ALIASES#28
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
pierreprinetti:patch-1

Conversation

@pierreprinetti
Copy link
Member

Remove pierreprinetti

Remove pierreprinetti
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 24, 2026
@openshift-ci-robot
Copy link

@pierreprinetti: This pull request explicitly references no jira issue.

Details

In response to this:

Remove pierreprinetti

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from gryf and stephenfin March 24, 2026 13:26
@stephenfin
Copy link

/ok-to-test
/approve
/lgtm
/override ci/prow/e2e-hypershift

@openshift-ci openshift-ci bot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Mar 26, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 26, 2026
@openshift-ci
Copy link

openshift-ci bot commented Mar 26, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: stephenfin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 26, 2026
@openshift-ci
Copy link

openshift-ci bot commented Mar 26, 2026

@stephenfin: Overrode contexts on behalf of stephenfin: ci/prow/e2e-hypershift

Details

In response to this:

/ok-to-test
/approve
/lgtm
/override ci/prow/e2e-hypershift

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.

@stephenfin
Copy link

/override ci/prow/e2e-openstack-capi-techpreview
/verified bypass

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 26, 2026
@openshift-ci-robot
Copy link

@stephenfin: The verified label has been added.

Details

In response to this:

/override ci/prow/e2e-openstack-capi-techpreview
/verified bypass

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link

openshift-ci bot commented Mar 26, 2026

@stephenfin: Overrode contexts on behalf of stephenfin: ci/prow/e2e-openstack-capi-techpreview

Details

In response to this:

/override ci/prow/e2e-openstack-capi-techpreview
/verified bypass

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-merge-bot openshift-merge-bot bot merged commit d7ec93a into openshift:main Mar 26, 2026
10 checks passed
@openshift-ci
Copy link

openshift-ci bot commented Mar 26, 2026

@pierreprinetti: all tests passed!

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants