Skip to content

Remove devppratik from OWNERS#115

Open
devppratik wants to merge 1 commit into
openshift:masterfrom
devppratik:remove-devppratik-from-owners
Open

Remove devppratik from OWNERS#115
devppratik wants to merge 1 commit into
openshift:masterfrom
devppratik:remove-devppratik-from-owners

Conversation

@devppratik

@devppratik devppratik commented Jun 12, 2026

Copy link
Copy Markdown

Offboarding myself from OWNERS

Summary by CodeRabbit

  • Chores
    • Removed a reviewer from the OWNERS file configuration.

Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
@coderabbitai

coderabbitai Bot commented Jun 12, 2026

Copy link
Copy Markdown

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: 430b55fd-35e2-4f53-95a5-38079aa464d8

📥 Commits

Reviewing files that changed from the base of the PR and between d9e58c9 and c5fcb41.

📒 Files selected for processing (1)
  • OWNERS
💤 Files with no reviewable changes (1)
  • OWNERS

Walkthrough

This PR removes devppratik from the reviewers list in the OWNERS configuration file. The approvers and maintainers lists remain unchanged. This is a single-line deletion from the project's owner and reviewer metadata.

Changes

OWNERS metadata update

Layer / File(s) Summary
Remove reviewer from OWNERS list
OWNERS
The devppratik entry is deleted from the reviewers section while all other entries remain unchanged.

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately and concisely describes the main change: removing devppratik from the OWNERS file, which aligns with the actual changeset and PR objectives.
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 No Ginkgo tests found: *_test.go files contain neither onsi/ginkgo/ginkgo. nor It("/Describe(" titles. PR only changes OWNERS, so no unstable Ginkgo titles were introduced.
Test Structure And Quality ✅ Passed Repo content for this PR only changes root OWNERS; no Ginkgo test code exists/changes to review. OWNERS no longer contains devppratik and there are no other file diffs visible.
Microshift Test Compatibility ✅ Passed PR #115 modifies only OWNERS (1 deletion) and no Ginkgo e2e test files were added/changed, so there are no new MicroShift compatibility concerns to flag.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR only updates OWNERS (removes devppratik). Repo contains no non-vendored Ginkgo e2e tests, so no new SNO multi-node assumptions were introduced.
Topology-Aware Scheduling Compatibility ✅ Passed The commit is titled “Remove devppratik from OWNERS”, and current OWNERS contains only reviewers/approvers/maintainers without devppratik; no deployment/operator/controller scheduling changes are i...
Ote Binary Stdout Contract ✅ Passed Local repo shows no file diffs and contains no devppratik; OWNERS-only offboarding can’t affect OTE JSON-over-stdout contract.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR #115 only changes OWNERS (removes devppratik) and does not add/modify any Ginkgo e2e tests, so no IPv4/IPv6 or external-connectivity assumptions to flag.
No-Weak-Crypto ✅ Passed PR only changes OWNERS. Repo scan for MD5/SHA1/DES/RC4/3DES/Blowfish/ECB plus token/secret compare patterns found 0 matches.
Container-Privileges ✅ Passed PR #115 only modifies the repository OWNERS file (removes devppratik); no container/K8s manifests or PodSecurity-related fields (hostPID/hostNetwork/hostIPC/privileged/SYS_ADMIN/allowPrivilegeEscal...
No-Sensitive-Data-In-Logs ✅ Passed PR only updates OWNERS reviewer list; OWNERS contains only GitHub usernames and no email/API-key/password/token patterns, so it doesn’t introduce sensitive logging.

✏️ 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.

Warning

⚠️ This pull request might be slop. It has been flagged by CodeRabbit slop detection and should be reviewed carefully.

@openshift-ci openshift-ci Bot requested review from bmeng and ravitri June 12, 2026 05:08
@openshift-ci

openshift-ci Bot commented Jun 12, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: devppratik
Once this PR has been reviewed and has the lgtm label, please assign rogbas 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:

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 commented Jun 12, 2026

Copy link
Copy Markdown

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant