Repository navigation
Conversation
Working group members should be able to push branches to experimental-ext-triggers-events and open pull requests from them, without being able to approve or administer the repository. Today the single triggers-events-wg team holds admin, so any new member would get all of that. Follow the ext-skills pattern. Add a triggers-events-wg-leads team nested under triggers-events-wg and give it admin. Drop triggers-events-wg to push. The two current members become leads, so their access does not change. Add tsarlandie-oai as a working group member. The repository's CODEOWNERS must name the leads team for this to take full effect. That is a separate change in that repository.
Pulumi PreviewClick to expand preview output |
pja-ant
marked this pull request as ready for review
October 9, 2026 18:47
This branch was successfully deployed
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
1 participant
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.
Summary
Lets Triggers & Events Working Group members push branches to
experimental-ext-triggers-eventsand open pull requests from them, without being able to approve merges or administer the repository. Adds @tsarlandie-oai (Thomas Sarlandie, OpenAI) as the first such member.Today the single
triggers-events-wgteam holdsadminand is the repository's only code owner. Any new member would get all of that. This follows theext-skillspattern, whereskills-over-mcp-wghaspushandskills-over-mcp-wg-leadshasadmin:triggers-events-wg-leadsrole and team, nested undertriggers-events-wg.adminon the repository and dropstriggers-events-wgtopush.tsarlandie-oaitotriggers-events-wgwith his Discord ID. No Workspace account is requested.The org ruleset on the default branch requires a code-owner approval. A companion change in
experimental-ext-triggers-eventspoints CODEOWNERS at the leads team. It has to merge after this is deployed, because the team does not exist until then.With
push, a member can still press Merge on a pull request once a lead has approved it. Nothing here restricts that.Test plan
Ran
prettier --checkon the four changed files,scripts/validate-config.ts("All references are valid") andscripts/test-config.ts(79 passed, 0 failed). A localnpm cifailed on a registry error, so I ran the scripts with an existingprettierandtsxand did not runnpm run checkorpulumi preview. CI covers both.