Repository navigation
Add Poita as a second GitHub account for pja-ant - #219
Merged
Merged
Conversation
Both accounts belong to the same person and get the same roles. The Discord ID and Google Workspace fields move to the Poita entry because those resources are keyed per person, so only one entry can carry them. This is a no-op for Discord and Google; the only new resources are Poita's GitHub team memberships.
Pulumi PreviewClick to expand preview output |
pja-ant
marked this pull request as ready for review
October 16, 2026 12:45
dsp-ant
approved these changes
Oct 16, 2026
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
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.
Summary
Adds
Poita, my personal GitHub account, alongsidepja-antwith the same roles, so my access isn't tied to a single GitHub account.pja-antkeeps all of its current roles and team memberships.The Discord ID and Google Workspace fields move from the
pja-antentry to thePoitaentry. Those can only live on one entry per person: the Discord role sync resource is named after the Discord ID (a second copy would be a duplicate Pulumi resource), andgoogleEmailPrefixis validated as unique. The resource names and role set are unchanged, so this is a no-op for Discord and Google.Poitais not yet an org member, so the deploy will send an org invite.Reviewer notes
core-maintainerson two accounts. The two accounts must never author and approve the same PR. This is temporary: a follow-up will remove thepja-antentry, which with the identity fields already onPoitais a single-block delete touching only GitHub team memberships.Poita: I'll comment on this PR from that account before marking it ready.Poitaonly the working-group andmaintainersroles now and movecore-maintainersover in the follow-up. Happy to do that instead.Test plan
npm run checkpasses locally (Prettier,validate-config, 79/79 config tests), and there are no duplicate Discord IDs, Google emails, or case-insensitive GitHub usernames acrossMEMBERS.Pulumi preview on this PR: 8 creates, all
Poita-<team>team memberships. No deletes, and nothing for Discord role sync or Google group membership. The no-opGroupSettings/OrgUnitupdates it also lists appear identically on #215 and #216.