Skip to content

Conversation

@joshbranham
Copy link
Contributor

In #723 a refactor was done to make testing easier for this package. However, it turns out that was not tested functionally and there were a few issues. This fixes those issues.

In openshift#723 a refactor was done to make testing easier
for this package. However, it turns out that was not tested functionally and there were
a few issues. This fixes those issues.
@joshbranham joshbranham self-assigned this May 14, 2025
@openshift-ci openshift-ci bot requested review from dustman9000 and typeid May 14, 2025 15:37
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 14, 2025
@joshbranham joshbranham changed the title Fix issues with osdctl promote saas OSD-30081: Fix issues with osdctl promote saas May 14, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 14, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 14, 2025

@joshbranham: This pull request references OSD-30081 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 bug to target the "4.20.0" version, but no target version was set.

Details

In response to this:

In #723 a refactor was done to make testing easier for this package. However, it turns out that was not tested functionally and there were a few issues. This fixes those issues.

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 May 14, 2025

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

}

/*
// Not in use
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hm

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unsure why this was commented out as "not in use" versus just being removed.

Copy link
Member

@typeid typeid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 14, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joshbranham, typeid

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

@joshbranham
Copy link
Contributor Author

Btw, I ran this locally with the fixes and it produced a valid branch and pushed it 👍

@openshift-merge-bot openshift-merge-bot bot merged commit 18b1de3 into openshift:master May 14, 2025
6 checks passed
@joshbranham joshbranham deleted the bug/fix-promote-command branch May 14, 2025 16:40
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.

3 participants