Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NO-JIRA: Finish Alerting Refactor #306

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

PeterYurkovich
Copy link
Contributor

/hold

Since OU-561 was completed without finishing the refactor, this PR looks to finalize the Alerting refactor. Pulling out the final two pages into their own files, and removing the routing entrypoint of the monitoring UI from the alerting.tsx file to a new router.tsx file.

We should hold this PR until everyone is back in January

@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 Dec 20, 2024
@openshift-ci openshift-ci bot requested review from jgbernalp and kyoto December 20, 2024 01:38
Copy link
Contributor

openshift-ci bot commented Dec 20, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: PeterYurkovich

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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 Dec 20, 2024
@PeterYurkovich PeterYurkovich changed the title Split alertrulesdetailpage out into separate file NO-JIRA: Finish Alerting Refactor Dec 20, 2024
@openshift-ci-robot
Copy link

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

In response to this:

/hold

Since OU-561 was completed without finishing the refactor, this PR looks to finalize the Alerting refactor. Pulling out the final two pages into their own files, and removing the routing entrypoint of the monitoring UI from the alerting.tsx file to a new router.tsx file.

We should hold this PR until everyone is back in January

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 20, 2024
@jgbernalp
Copy link
Contributor

/retest

@PeterYurkovich
Copy link
Contributor Author

Don't worry about retesting this PR for now, as the tests will likely need to be rerun regardless in the new year

@PeterYurkovich
Copy link
Contributor Author

/retest

@PeterYurkovich
Copy link
Contributor Author

@juzhao could you please check this PR for regressions?

Copy link
Contributor

openshift-ci bot commented Jan 3, 2025

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

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 10, 2025
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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.

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants