chore: replace CODEOWNERS owners with @vivek-devtron by claude[bot] · Pull Request #7064 · devtron-labs/devtron · GitHub
Skip to content

chore: replace CODEOWNERS owners with @vivek-devtron - #7064

Draft
claude[bot] wants to merge 1 commit into
mainfrom
claude/codeowners-vivek-devtron-only
Draft

claude[bot] wants to merge 1 commit into
mainfrom
claude/codeowners-vivek-devtron-only

Conversation

@claude

@claude claude Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Requested by Abhibhaw · Slack thread

Description

Before: .github/CODEOWNERS listed @prakarsh-dt alongside @vivek-devtron on every rule, with the catch-all rule being * @prakarsh-dt @vivek-devtron. The .github/ rule was @prakarsh-dt @tayalrishabh96 @pawan-59 @vivek-devtron and the specs/ rule was @prakarsh-dt @pawan-59 @vivek-devtron.

After: @prakarsh-dt is removed and @vivek-devtron is the owner of every rule, so the catch-all is now * @vivek-devtron. The .github/ rule is @vivek-devtron @tayalrishabh96 @pawan-59 and the specs/ rule is @vivek-devtron @pawan-59. The other requested handles (@pawan-mehta-dt, @nishant-d, @deepak-devtron, @vikramdevtron) were not present in the file. @tayalrishabh96 and @pawan-59 are untouched.

This was done by editing only .github/CODEOWNERS, deduplicating @vivek-devtron where it appeared once per line; no code changes are included.

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR requires documentation updates?
  • I've updated documentation as required by this PR.
  • I have performed a self-review of my own code.

Does this PR introduce a user-facing change?


🤖 Generated with Claude Code

https://claude.ai/code/session_01R55HHNM9GyjiaH4zjhNyds

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01R55HHNM9GyjiaH4zjhNyds
@bito-code-review

Copy link
Copy Markdown

@sonarqubecloud

Copy link
Copy Markdown

This branch has not been deployed

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant