managed-cluster-config
managed-cluster-config copied to clipboard
OCPBUGS-55803: add legacy branding
What type of PR is this?
Cleanup
What this PR does / why we need it?
Utilizes official ROSA product branding for supported versions, continue using legacy branded for older versions to not break them.
Which Jira/Github issue(s) this PR fixes?
Resolves OCPBUGS-56264, OCPBUGS-55803. Supersedes #2426.
Special notes for your reviewer:
Pre-checks (if applicable):
- [ ] Tested latest changes against a cluster (this will need to be tested after deployment)
linking the issue to Jira:
/retitle OCPBUGS-56264, OCPBUGS-55803: add legacy branding
@iamkirkbater: This pull request references Jira Issue OCPBUGS-56264, which is valid. The bug has been moved to the POST state.
3 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.20.0) matches configured target version for branch (4.20.0)
- bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
Requesting review from QA contact: /cc @yapei
The bug has been updated to refer to the pull request using the external bug tracker.
This pull request references Jira Issue OCPBUGS-55803, which is valid. The bug has been moved to the POST state.
3 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.20.0) matches configured target version for branch (4.20.0)
- bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
Requesting review from QA contact: /cc @yapei
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
What type of PR is this?
Cleanup
What this PR does / why we need it?
Utilizes official ROSA product branding for supported versions, continue using legacy branded for older versions to not break them.
Which Jira/Github issue(s) this PR fixes?
Resolves OCPBUGS-56264, OCPBUGS-55803. Supersedes #2426.
Special notes for your reviewer:
Pre-checks (if applicable):
- [ ] Tested latest changes against a cluster (this will need to be tested after deployment)
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.
/retitle OCPBUGS-55803: add legacy branding
@iamkirkbater: This pull request references Jira Issue OCPBUGS-55803, which is valid.
3 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.20.0) matches configured target version for branch (4.20.0)
- bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
Requesting review from QA contact: /cc @yapei
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
What type of PR is this?
Cleanup
What this PR does / why we need it?
Utilizes official ROSA product branding for supported versions, continue using legacy branded for older versions to not break them.
Which Jira/Github issue(s) this PR fixes?
Resolves OCPBUGS-56264, OCPBUGS-55803. Supersedes #2426.
Special notes for your reviewer:
Pre-checks (if applicable):
- [ ] Tested latest changes against a cluster (this will need to be tested after deployment)
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.
@iamkirkbater: all tests passed!
Full PR test history. Your PR dashboard.
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: iamkirkbater, rafael-azevedo
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [iamkirkbater,rafael-azevedo]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@iamkirkbater: Jira Issue OCPBUGS-55803: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-55803 has been moved to the MODIFIED state.
In response to this:
What type of PR is this?
Cleanup
What this PR does / why we need it?
Utilizes official ROSA product branding for supported versions, continue using legacy branded for older versions to not break them.
Which Jira/Github issue(s) this PR fixes?
Resolves OCPBUGS-56264, OCPBUGS-55803. Supersedes #2426.
Special notes for your reviewer:
Pre-checks (if applicable):
- [ ] Tested latest changes against a cluster (this will need to be tested after deployment)
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.