NO-JIRA: Add approvers and reviewers to helm-plugin OWNERS

[sowmya-sl]

The helm-plugin OWNERS file only had a component label. Add dedicated approvers and reviewers to ensure helm-plugin changes are reviewed by helm team.

Summary by CodeRabbit

• Chores
  • Updated the OWNERS file to explicitly define approvers and reviewers for the helm-plugin package, establishing clearer governance and review responsibilities.

[coderabbitai]

📝 Walkthrough

Walkthrough

The OWNERS file for the Helm plugin package was updated to define explicit governance structure. Two new sections were added—approvers and reviewers—each specifying four team members responsible for code review and approval decisions. The existing component/helm label remains in place. This change is purely additive, establishing clear ownership and review responsibilities for the Helm plugin module within the frontend packages directory structure.

🚥 Pre-merge checks | ✅ 11 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description explains the rationale but does not follow the required template with sections like Analysis, Solution, Test cases, or Browser conformance.	Fill out the required description template with at least Analysis/Root cause and Solution description sections to ensure proper triage and review.

✅ Passed checks (11 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	This PR only modifies the OWNERS file and does not add, modify, or change any Ginkgo test files, making it not applicable to the Stable and Deterministic Test Names check.
Test Structure And Quality	✅ Passed	PR modifies only OWNERS config file with no Ginkgo test code present, making the test quality check inapplicable.
Microshift Test Compatibility	✅ Passed	PR modifies only OWNERS metadata file without adding any new Ginkgo e2e tests, Go test files, or test code.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR modifies only OWNERS file; no new Ginkgo e2e tests present, so SNO compatibility check not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	PR modifies only OWNERS file for governance configuration, not workload specifications or scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	Pull request modifies only OWNERS governance file in helm-plugin frontend package; zero changes to executable code, Go binaries, or process-level test setup.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PR modifies only frontend/packages/helm-plugin/OWNERS file for RBAC configuration; contains no Ginkgo e2e test code.
Title check	✅ Passed	The title accurately and concisely describes the main change: adding approvers and reviewers sections to the helm-plugin OWNERS file.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

@sowmya-sl: 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.

[webbnh]

/LGTM

@sowmya-sl, I think you'll want to add the NO-JIRA prefix to the PR title, and you'll probably need a /verified by....

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sowmya-sl, webbnh
Once this PR has been reviewed and has the lgtm label, please assign logonoff for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• frontend/OWNERS

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

[openshift-ci-robot]

@sowmya-sl: This pull request explicitly references no jira issue.

Details

In response to this:

The helm-plugin OWNERS file only had a component label. Add dedicated approvers and reviewers to ensure helm-plugin changes are reviewed by helm team.

Summary by CodeRabbit

• Chores
• Updated the OWNERS file to explicitly define approvers and reviewers for the helm-plugin package, establishing clearer governance and review responsibilities.

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.

[sowmya-sl]

/verified by @sowmya-sl

[openshift-ci-robot]

@sowmya-sl: This PR has been marked as verified by @sowmya-sl.

Details

In response to this:

/verified by @sowmya-sl

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.

[webbnh]

/assign logonoff

[logonoff]

/label px-approved
/label docs-approved
/assign @jhadvig