Closed BigLep closed 3 months ago
The following access changes will be introduced as a result of applying the plan:
Before merge, verify that all the following plans are correct. They will be applied as-is after the merge.
@BigLep what do we need to do to get this merged ?
@BigLep what do we need to do to get this merged ?
I was waiting until the repo became publish so those affected could be notified with @mention and see the PR. I'll take care of it this week (week of 2024-08-12).
[@mentioned below the folks who are having their permissions affected so they get a notification about this change]
If you are receiving this message, your permissions to repos that labbers
had access to may have been adjusted.
https://github.com/filecoin-project/github-mgmt/pull/48 provides more context for the change. It also summarizes the changes that were made at the repo/team level.
An individual-collaborator-focused view of the changes (i.e., what changes are happening for me?) is viewable at https://github.com/filecoin-project/github-mgmt/pull/48#issuecomment-2243756429
Feedback or questions welcome, but I am planning to merge this now given:
If I got any of this wrong we can revert or amend.
Thanks, Steve
@mentioning the others who affected but didn't get notification in https://github.com/filecoin-project/github-mgmt/pull/48#issuecomment-2292020817 because of GitHub @mention limits.
Summary
Took the current
labbers
team and used it to seed an alumni team. Thelabbers
team has been deleted.Why do you need this?
"labbers" is a historical construct. Given it doesn't exist anymore, it shouldn't be a vehicle for permissions.
Overview of changes
Below are the set of changes that affect the
labbers
team by its removal.Reviewer's Checklist