Skip to content

Conversation

@jcmoraisjr
Copy link
Contributor

Add a new make target on hack Makefile to update image without the need to push to a registry.

Add a new make target on hack Makefile to update image without the need to push to a registry.
@openshift-ci openshift-ci bot requested review from candita and ironcladlou January 14, 2026 18:31
@gcs278
Copy link
Contributor

gcs278 commented Jan 14, 2026

Thanks for the update! It looks good.

/lgtm

I think if you add NO-JIRA: to the title of your PR, it will magically bypass the PR label requirements in tide (it's been awhile for me so I'm not 100% sure).

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 14, 2026
@jcmoraisjr jcmoraisjr changed the title Hack: update image without push NO-JIRA: hack: update image without push Jan 15, 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 15, 2026
@openshift-ci-robot
Copy link
Contributor

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

Details

In response to this:

Add a new make target on hack Makefile to update image without the need to push to a registry.

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.

@jcmoraisjr
Copy link
Contributor Author

/retest

@alebedev87
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 23, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alebedev87

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 Jan 23, 2026
@alebedev87
Copy link
Contributor

/verified by CI

Hacking changes only.

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

@alebedev87: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

Hacking changes only.

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
Contributor

openshift-ci bot commented Jan 23, 2026

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

@openshift-merge-bot openshift-merge-bot bot merged commit 9db967e into openshift:master Jan 23, 2026
10 checks passed
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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants