Repository navigation
Conversation
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Peter · project thread
Summary
Points CODEOWNERS at
@modelcontextprotocol/tasks-events-wg-leadsin 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 onmainrequires 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 thetasks-events-wg-leadsteam from modelcontextprotocol/access#226. Also updates the stale repository name in the file header.Test plan
tasks-events-wg-leadsexists and already has access to this repository.Generated by Claude Code