Skip to content

OU-1240: [release-coo-ocp-4.22] Makefile and package.json to enable test-frontend-ci - #1092

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-coo-ocp-4.22from
openshift-cherrypick-robot:cherry-pick-1091-to-release-coo-ocp-4.22
Jul 24, 2026
Merged

OU-1240: [release-coo-ocp-4.22] Makefile and package.json to enable test-frontend-ci#1092
openshift-merge-bot[bot] merged 1 commit into
openshift:release-coo-ocp-4.22from
openshift-cherrypick-robot:cherry-pick-1091-to-release-coo-ocp-4.22

Conversation

@openshift-cherrypick-robot

Copy link
Copy Markdown

This is an automated cherry-pick of #1091

/assign etmurasaki

@openshift-ci-robot

openshift-ci-robot commented Jul 24, 2026

Copy link
Copy Markdown

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: OU-1240

Details

In response to this:

This is an automated cherry-pick of #1091

/assign etmurasaki

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 commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: 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.

@jgbernalp

Copy link
Copy Markdown
Contributor

/lgtm

@jgbernalp jgbernalp changed the title [release-coo-ocp-4.22] OU-1240: Makefile and package.json to enable test-frontend-ci OU-1240: [release-coo-ocp-4.22] Makefile and package.json to enable test-frontend-ci Jul 24, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 24, 2026
@jgbernalp

Copy link
Copy Markdown
Contributor

/label qe-approved

@openshift-ci

openshift-ci Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgbernalp, openshift-cherrypick-robot

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. qe-approved Signifies that QE has signed off on this PR labels Jul 24, 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 Jul 24, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 24, 2026

Copy link
Copy Markdown

@openshift-cherrypick-robot: This pull request references OU-1240 which is a valid jira issue.

Details

In response to this:

This is an automated cherry-pick of #1091

/assign etmurasaki

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-merge-bot
openshift-merge-bot Bot merged commit 89a04ea into openshift:release-coo-ocp-4.22 Jul 24, 2026
6 checks passed
@etmurasaki

Copy link
Copy Markdown
Contributor

/cherry-pick release-coo-ocp-4.19

@openshift-cherrypick-robot

Copy link
Copy Markdown
Author

@etmurasaki: new pull request created: #1093

Details

In response to this:

/cherry-pick release-coo-ocp-4.19

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.

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. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants