Skip to content

Comments

NO-JIRA: OWNERS: Add angelcerveraroldan#1883

Open
angelcerveraroldan wants to merge 1 commit intoopenshift:masterfrom
angelcerveraroldan:add-owner-angelcr
Open

NO-JIRA: OWNERS: Add angelcerveraroldan#1883
angelcerveraroldan wants to merge 1 commit intoopenshift:masterfrom
angelcerveraroldan:add-owner-angelcr

Conversation

@angelcerveraroldan
Copy link

No description provided.

@openshift-ci openshift-ci bot requested review from HuijingHei and travier January 12, 2026 13:11
@aaradhak
Copy link
Contributor

@angelcerveraroldan : In this case , we would need to add a "NO-JIRA: " prefix in the PR title, something like the below

NO-JIRA: OWNERS: add angelcerveraroldan

By adding that, it would satisfy the tide CI requirement.

@aaradhak
Copy link
Contributor

/lgtm
/approve

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 13, 2026
@aaradhak
Copy link
Contributor

/verified by @aaradhak

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

@aaradhak: This PR has been marked as verified by @aaradhak.

Details

In response to this:

/verified by @aaradhak

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.

@angelcerveraroldan angelcerveraroldan changed the title OWNERS: Add angelcerveraroldan NO-JIRA: OWNERS: Add angelcerveraroldan Jan 13, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 13, 2026
@openshift-ci-robot
Copy link

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

Details

In response to this:

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.

@HuijingHei
Copy link
Contributor

/acknowledge-critical-fixes-only

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 14, 2026
@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Jan 19, 2026
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 19, 2026
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 19, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 16, 2026

@angelcerveraroldan: 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.

@cverna
Copy link
Contributor

cverna commented Feb 19, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 19, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 19, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aaradhak, angelcerveraroldan, cverna

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

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants