Model the maintainers group as a GitHub team with write on spec and read on maintainer-docs - #146
Merged
Merged
Conversation
Adds a GitHub team for the existing 'maintainers' role (previously Discord/Google only, with no parent team so it does not inherit steering-committee repo permissions) and grants it pull access to the maintainer-docs repository. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LRucdTmghybeWkeaTtVuS1
Pulumi PreviewClick to expand preview output |
localden
marked this pull request as ready for review
September 4, 2026 06:47
Complete the maintainers group model: the parentless maintainers GitHub team (added in this PR alongside its existing Discord role and Google group) now gets push on modelcontextprotocol/modelcontextprotocol in addition to pull on maintainer-docs. Branch protection on the spec repo still requires changes to land via pull requests. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V6sAnrWknVzWzfuuzomMXk
claude
Bot
changed the title
localden
approved these changes
Sep 4, 2026
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
2 participants
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 Den Delimarsky · Slack thread
Before: the
maintainersgroup exists only as a Discord role and a Google group — it has no GitHub presence at all. There is nomaintainersGitHub team, no access to the spec repo through this group, and no access tomaintainer-docs.After: a
maintainersGitHub team exists and is managed here like every other team. It has write (push) access on the spec repo (modelcontextprotocol/modelcontextprotocol) — branch protection there still requires changes to land via pull requests intomain— and read (pull) access onmaintainer-docs, so everyone holding themaintainersrole inusers.tscan read the docs site.How:
src/config/roles.tsaddsgithub: { team: 'maintainers' }to the existingmaintainersrole, keeping its Discord role, Google group, and user provisioning unchanged. The team deliberately has no parent so it does not inheritsteering-committeerepo permissions.src/config/repoAccess.tsadds{ team: 'maintainers', permission: 'push' }to themodelcontextprotocol(spec) entry and{ team: 'maintainers', permission: 'pull' }to themaintainer-docsentry.npm run checkpasses locally (format, validate, 33/33 config tests). The Pulumi preview will show the newmaintainersteam, memberships for users holding that role, and the two repo permission grants.🤖 Generated with Claude Code
https://claude.ai/code/session_01V6sAnrWknVzWzfuuzomMXk