Skip to content

Conversation

@bentito
Copy link
Contributor

@bentito bentito commented Apr 1, 2024

To make the downstream repos self explanatory we need to link to the information about how the downstreaming process works.

@openshift-ci openshift-ci bot requested review from m1kola and perdasilva April 1, 2024 16:31
@bentito
Copy link
Contributor Author

bentito commented Apr 1, 2024

/test verify-commits

@bentito bentito changed the title Add pointer to tooling README for downstreaming info ✨ Add pointer to tooling README for downstreaming info Apr 1, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 1, 2024

@bentito: 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/test-infra repository. I understand the commands that are listed here.

@kevinrizza
Copy link
Member

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 3, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 3, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bentito, kevinrizza

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 Apr 3, 2024
@bentito bentito changed the title ✨ Add pointer to tooling README for downstreaming info OPRUN-3268 Add pointer to tooling README for downstreaming info Apr 3, 2024
@kevinrizza
Copy link
Member

/jira refresh

@openshift-ci-robot
Copy link

@kevinrizza: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

/jira refresh

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.

@bentito bentito changed the title OPRUN-3268 Add pointer to tooling README for downstreaming info OPRUN-3268: Add pointer to tooling README for downstreaming info Apr 3, 2024
@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 3, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 3, 2024

@bentito: This pull request references OPRUN-3268 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.16.0" version, but no target version was set.

Details

In response to this:

To make the downstream repos self explanatory we need to link to the information about how the downstreaming process works.

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.

@bentito
Copy link
Contributor Author

bentito commented Apr 3, 2024

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 3, 2024

@bentito: This pull request references OPRUN-3268 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.16.0" version, but no target version was set.

Details

In response to this:

/jira refresh

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 6ae54a9 into openshift:main Apr 3, 2024
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-olm-operator-controller-container-v4.16.0-202404031748.p0.g6ae54a9.assembly.stream.el9 for distgit ose-olm-operator-controller.
All builds following this will include this PR.

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.

4 participants