Skip to content

COO-1532: Merge Dashboards Feature into main#764

Merged
openshift-merge-bot[bot] merged 42 commits intomainfrom
customizable-dashboards
Feb 11, 2026
Merged

COO-1532: Merge Dashboards Feature into main#764
openshift-merge-bot[bot] merged 42 commits intomainfrom
customizable-dashboards

Conversation

@PeterYurkovich
Copy link
Contributor

/label tide/merge-method-squash

zhuje and others added 30 commits October 14, 2025 14:20
OU-888: Perses Dashboards Integrate  panel editing
OU-1023: Integrate remotePluginLoader()
OU-1008: Perses Variable Editing Panel
OU-1064: including data-test into perses components for automation
…ith-main

NO-JIRA: Sync customizable dashboards with main
OU-1172:  [Edit Dashboards] - Remove "Edit Datasources" button from Editor toolbar
OU-1158:  [List Perses] - Change Namespace is throwing 404
OU-1163: use namespace for edit permission check
OU-1170: Fix Add Variable - Name with more than 75 chars
…ustom, remove <PageSection /> because we are overriding padding
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 11, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 11, 2026

@PeterYurkovich: This pull request references COO-1532 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 task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

/label tide/merge-method-squash

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 the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Feb 11, 2026
@openshift-ci openshift-ci bot requested review from etmurasaki and zhuje February 11, 2026 14:40
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 11, 2026
@PeterYurkovich
Copy link
Contributor Author

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 11, 2026
OU-1196: update perses dependencies
@PeterYurkovich
Copy link
Contributor Author

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 11, 2026
@etmurasaki
Copy link
Contributor

etmurasaki commented Feb 11, 2026

/label qe-approved
to be tested all together with OU-1195

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Feb 11, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 11, 2026

@PeterYurkovich: This pull request references COO-1532 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 task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

/label tide/merge-method-squash

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.

@jgbernalp
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 11, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 11, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgbernalp, PeterYurkovich

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:
  • OWNERS [PeterYurkovich,jgbernalp]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jgbernalp
Copy link
Contributor

/test ?

@jgbernalp
Copy link
Contributor

/test e2e-dashboards

@PeterYurkovich
Copy link
Contributor Author

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 11, 2026

@PeterYurkovich: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-dashboards b97cf05 link false /test e2e-dashboards

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 ee45e94 into main Feb 11, 2026
9 of 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. qe-approved Signifies that QE has signed off on this PR tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants