Skip to content

MERGE CONFLICT! NO-JIRA: Branch Sync master to release-4.22 [04-15-2026]#3142

Draft
openshift-pr-manager[bot] wants to merge 3 commits intorelease-4.22from
sync-master-to-release-4.22-04-15-2026
Draft

MERGE CONFLICT! NO-JIRA: Branch Sync master to release-4.22 [04-15-2026]#3142
openshift-pr-manager[bot] wants to merge 3 commits intorelease-4.22from
sync-master-to-release-4.22-04-15-2026

Conversation

@openshift-pr-manager
Copy link
Copy Markdown

Automated branch sync: master to release-4.22.

jcaamano and others added 3 commits April 10, 2026 14:47
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
NO-JIRA: openshift tests: demote to informing
@openshift-pr-manager openshift-pr-manager Bot changed the title NO-JIRA: Branch Sync master to release-4.22 [04-15-2026] MERGE CONFLICT! NO-JIRA: Branch Sync master to release-4.22 [04-15-2026] Apr 15, 2026
@openshift-pr-manager
Copy link
Copy Markdown
Author

/hold
needs conflict resolution

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 15, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@openshift-pr-manager[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

Automated branch sync: master to release-4.22.

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 added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Apr 15, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 15, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-pr-manager[bot]
Once this PR has been reviewed and has the lgtm label, please assign martinkennelly for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 15, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants