Skip to content

chore: rm past Forest team members - #201

Merged
rjan90 merged 2 commits into
filecoin-project:masterfrom
LesnyRumcajs:master
Apr 2, 2026
Merged

chore: rm past Forest team members#201
rjan90 merged 2 commits into
filecoin-project:masterfrom
LesnyRumcajs:master

Conversation

@LesnyRumcajs

Copy link
Copy Markdown
Contributor

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

  • It is clear where the request is coming from (if unsure, ask)
  • All the automated checks passed
  • The YAML changes reflect the summary of the request
  • The Terraform plan posted as a comment reflects the summary of the request

@LesnyRumcajs
LesnyRumcajs requested a review from a team as a code owner March 31, 2026 14:36
@github-actions

github-actions Bot commented Mar 31, 2026

Copy link
Copy Markdown
Contributor

The following access changes will be introduced as a result of applying the plan:

Access Changes
There will be no access changes

@rjan90

rjan90 commented Mar 31, 2026

Copy link
Copy Markdown
Contributor

I'm removing elmattic for the 3+ time, some faulty sync job seems to be constantly bringing him back.

Okay, that is weird 👀. Will have to investigate where that could be coming from

@rjan90

rjan90 commented Mar 31, 2026

Copy link
Copy Markdown
Contributor

I'm removing elmattic for the 3+ time, some faulty sync job seems to be constantly bringing him back.

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.

@LesnyRumcajs

Copy link
Copy Markdown
Contributor Author

Oh, that makes sense! I expected code is law, but I also should have RTFM 😁

@BigLep

BigLep commented Mar 31, 2026

Copy link
Copy Markdown
Member

I removed both from the UI. I have rerun sync: https://github.com/filecoin-project/github-mgmt/actions/runs/23810649187

@github-actions

Copy link
Copy Markdown
Contributor

Before merge, verify that all the following plans are correct. They will be applied as-is after the merge.

Terraform plans

filecoin-project

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

@LesnyRumcajs

Copy link
Copy Markdown
Contributor Author

@rjan90 Mergio?

@rjan90
rjan90 merged commit d57c3de into filecoin-project:master Apr 2, 2026
6 checks passed
@rvagg

rvagg commented Apr 2, 2026

Copy link
Copy Markdown
Member

merged a nothing-commit, did it even work? d57c3de

@rjan90

rjan90 commented Apr 2, 2026

Copy link
Copy Markdown
Contributor

Might a nothing commit, since it already got synced 🤔:

I removed both from the UI. I have rerun sync: https://github.com/filecoin-project/github-mgmt/actions/runs/23810649187

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants