Skip to content

Make the working group leads the code owners - #25

Open
poita wants to merge 1 commit into
mainfrom
poita/codeowners-wg-leads
Open

poita wants to merge 1 commit into
mainfrom
poita/codeowners-wg-leads

Conversation

@poita

@poita poita commented Nov 20, 2026

Copy link
Copy Markdown
Contributor

Requested by Peter · project thread

Summary

Points CODEOWNERS at @modelcontextprotocol/tasks-events-wg-leads in place of @modelcontextprotocol/tasks-events-wg, so that merge approval stays with the Tasks and Events WG leads now that working group members have push access. The org ruleset on main requires a code-owner approval, so naming the whole working group would let any member's approval count.

Replaces #12, which was opened from an old account, used the pre-rename team name, and now conflicts with main. This addresses @LucaButBoring's review there by using the tasks-events-wg-leads team from modelcontextprotocol/access#226. Also updates the stale repository name in the file header.

Test plan

  • tasks-events-wg-leads exists and already has access to this repository.
  • After merge, GitHub shows no error banner on CODEOWNERS and new PRs request review from the leads team.

Generated by Claude Code

Point CODEOWNERS at @modelcontextprotocol/tasks-events-wg-leads so that
merge approval stays with the Tasks and Events WG leads now that members
have push access.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QK1G3qHomeTLjunKLVe9Lf
@poita
poita requested a review from a team as a code owner November 20, 2026 10:52
@poita poita self-assigned this Nov 20, 2026
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