chore: add new approvers

[devppratik]

Adding folks from Team Hulk to be approvers

Summary by CodeRabbit

• Chores
  • Expanded the code review/maintainer reviewer list in repository configuration.

---

Note: This release contains no user-facing changes or features. This is an internal administrative update.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 5afd7f13-06d1-4722-becf-9e2e63b34ab2

📥 Commits

Reviewing files that changed from the base of the PR and between d11db4b and ec61949.

📒 Files selected for processing (1)

• OWNERS

✅ Files skipped from review due to trivial changes (1)

• OWNERS

---

Walkthrough

Five new GitHub usernames are added to the reviewers list in the OWNERS file.

Changes

Reviewer List Update

Layer / File(s)	Summary
Add reviewers to OWNERS OWNERS	The reviewers list is expanded with five new usernames: TheUndeadKing, chamalabey, charlesgong, rbhilare, and Tafhim.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title refers to adding approvers, but the change actually adds reviewers to the OWNERS file, not approvers. This is a terminology mismatch.	Update the title to accurately reflect that reviewers were added (e.g., 'chore: add new reviewers to OWNERS') rather than approvers.

✅ Passed checks (14 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
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	Scanned Go Ginkgo test titles (It/Describe/Context/When) for UUIDs, timestamps/dates, IPs, and generated pod/node/namespace suffix patterns; none found.
Test Structure And Quality	✅ Passed	PR #243 only updates OWNERS (adds approver/reviewer usernames); no Ginkgo test files are changed, so the test structure/quality checks are not applicable.
Microshift Test Compatibility	✅ Passed	PR #243 changes only the repository OWNERS file (add new approvers/reviewers) and does not add or modify any Ginkgo e2e tests, so MicroShift compatibility is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR #243 only changes the root OWNERS file (adds reviewers/approvers) and does not add/modify any Ginkgo e2e tests, so no SNO compatibility assumptions need review.
Topology-Aware Scheduling Compatibility	✅ Passed	PR #243 changes only the OWNERS file (adds approver/reviewer entries); it does not modify deployment manifests, operators, or controllers, so no HA-topology scheduling constraints were introduced.
Ote Binary Stdout Contract	✅ Passed	GitHub PR shows only OWNERS file updated (no Go/test/suite code changes), so no process-level stdout contract violations were introduced.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	In this checkout, the added usernames appear only in OWNERS/OWNERS_ALIASES (no networking/test code touched). The PR is OWNERS-only, so no new Ginkgo e2e IPv4/IPv6 or external connectivity assumpti...
No-Weak-Crypto	✅ Passed	PR #243 changes only the OWNERS file (adds usernames to approvers); it includes no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB usage or custom/non-constant-time crypto code.
Container-Privileges	✅ Passed	PR #243 changes only the OWNERS file; no container/K8s manifests or privilege fields (hostPID/hostNetwork/hostIPC/SYS_ADMIN/privileged/allowPrivilegeEscalation) were found on the PR files page.
No-Sensitive-Data-In-Logs	✅ Passed	Repo scan shows no logger lines emitting tokens/passwords/API keys/PII; only “Can't find value for secret key …” (key name, not secret value). PR appears to change OWNERS only.

_{✏️ 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.}

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 55.67%. Comparing base (7b90da7) to head (ec61949).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #243   +/-   ##
=======================================
  Coverage   55.67%   55.67%           
=======================================
  Files          23       23           
  Lines        1895     1895           
=======================================
  Hits         1055     1055           
  Misses        785      785           
  Partials       55       55           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[openshift-ci]

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

[tkong-redhat]

/lgtm

[tkong-redhat]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: devppratik, tkong-redhat

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 [tkong-redhat]

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