Restrict Skills WG admin access to WG leads - #190
Merged
Merged
Conversation
pja-ant
requested changes
Sep 17, 2026
pja-ant
approved these changes
Sep 17, 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
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.
The full Skills WG currently has admin access to
ext-skills. This separates repository administration from regular WG contributions.skills-over-mcp-wg-leadsteam underskills-over-mcp-wg, containing exactlysambhav,olaservo(Ola Hungerford), andpja-ant(Peter Alexander).push) onext-skills, allowing WG members to create branches and collaborate.Organization owners and the existing org-wide admin roles retain their access. Within the Skills WG, admin is granted only to the three leads.
Follow-up after the leads team exists: update
ext-skills/.github/CODEOWNERSto the leads team (it currently references the oldskills-over-mcp-igteam) and verify that branch protection requires code-owner approval. Write access alone does not enforce that review requirement.Validation: all 33 existing configuration tests and reference validation passed again after the review change, using Node 24's TypeScript support in a temporary copy with explicit import extensions. No infrastructure deployment was performed.