Skip to content

NO-JIRA: Remove @lunarwhite from OWNERS#403

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
lunarwhite:owner-update
Apr 10, 2026
Merged

NO-JIRA: Remove @lunarwhite from OWNERS#403
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
lunarwhite:owner-update

Conversation

@lunarwhite
Copy link
Copy Markdown
Contributor

@lunarwhite lunarwhite commented Apr 9, 2026

Removing myself from the OWNERS files in this repo.

(Now subfolder OWNERS is no longer required. We can rely solely on the root OWNERS.)

I cannot access Gmail, Slack or SSO since early today. :(

Farewell (for real this time) my friends. :)

/cc @bharath-b-rh @mytreya-rh @chiragkyal @swghosh

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 9, 2026
@openshift-ci-robot
Copy link
Copy Markdown

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

Details

In response to this:

Removing myself from the OWNERS files in this repo.

(Now subfolder OWNERS is no longer required. We can rely solely on the root OWNERS.)

I cannot access Gmail or SSO since early today. :(

Farewell (for real this time) my friends. :)

/cc @bharath-b-rh @mytreya-rh @chiragkyal @swghosh

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.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 9, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 95b296a8-8ca3-4cf4-a7d0-1932f6b3143f

📥 Commits

Reviewing files that changed from the base of the PR and between b2cb4d0 and 75b6ee0.

📒 Files selected for processing (2)
  • docs/OWNERS
  • test/OWNERS
💤 Files with no reviewable changes (2)
  • docs/OWNERS
  • test/OWNERS

Walkthrough

The pull request removes the complete contents of two OWNERS configuration files (docs/OWNERS and test/OWNERS), eliminating all previously defined reviewer and approver assignments.

Changes

Cohort / File(s) Summary
OWNERS Configuration
docs/OWNERS, test/OWNERS
Removed all reviewer and approver lists from both files, eliminating code review assignment configurations.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ 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 openshift-ci Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Apr 9, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 9, 2026

Hi @lunarwhite. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@chiragkyal
Copy link
Copy Markdown
Member

Farewell (for real this time) my friends. :)

I've no words :(

@bharath-b-rh
Copy link
Copy Markdown
Contributor

It's a pleasure working with you. Sad to see this happen. Wish you very good times ahead.

@bharath-b-rh
Copy link
Copy Markdown
Contributor

No user facing changes, hence adding all necessary labels.
/ok-to-test
/lgtm
/approve
/label docs-approved
/label qe-approved
/label px-approved

@openshift-ci openshift-ci Bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. docs-approved Signifies that Docs has signed off on this PR qe-approved Signifies that QE has signed off on this PR px-approved Signifies that Product Support has signed off on this PR and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 10, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 10, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 10, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bharath-b-rh, lunarwhite

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:

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 Apr 10, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 10, 2026

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

@openshift-merge-bot openshift-merge-bot Bot merged commit 9f2e305 into openshift:master Apr 10, 2026
8 checks passed
@lunarwhite lunarwhite deleted the owner-update branch April 10, 2026 05:23
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. docs-approved Signifies that Docs has signed off on this PR 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. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants