chore: rm past Forest team members#201
Conversation
|
The following access changes will be introduced as a result of applying the plan: Access Changes |
Okay, that is weird 👀. Will have to investigate where that could be coming from |
I dug into this: elmattic is not being re-added by a faulty repo-side sync. The weekly Sync workflow imports the current live GitHub org/team state back into github/filecoin-project.yml, and GitHub still shows elmattic as an active direct member of filecoin-project and an active member of Forest. That’s also why he was reintroduced after the earlier removal: PR #177 removed him from YAML, but the scheduled sync on November 9, 2025 added him back from live GitHub state. This repo intentionally blocks org-member removal via Terraform, so removing him from YAML alone is not enough, see https://github.com/filecoin-project/github-mgmt/blob/master/README.md#removing-members-from-the-organization and a org owner needs to remove him in the GitHub UI first, then run Sync. I was not aware of ^^ when accepting and merging your #177 PR, so now I will have to summon @BigLep first for removing these members from the GH UI as well. |
|
Oh, that makes sense! I expected code is law, but I also should have RTFM 😁 |
|
I removed both from the UI. I have rerun sync: https://github.com/filecoin-project/github-mgmt/actions/runs/23810649187 |
|
Before merge, verify that all the following plans are correct. They will be applied as-is after the merge. Terraform plansfilecoin-project |
|
@rjan90 Mergio? |
|
merged a nothing-commit, did it even work? d57c3de |
|
Might a nothing commit, since it already got synced 🤔:
|
Summary
Removing past Forest team members. Note: I'm removing elmattic for the 3+ time, some faulty sync job seems to be constantly bringing him back.
Why do you need this?
What else do we need to know?
DRI: myself
Reviewer's Checklist