Skip to content

Added LesnyRumcajs as an fvm-crate-owner #158

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 15, 2025

Conversation

BigLep
Copy link
Member

@BigLep BigLep commented Aug 15, 2025

Relevant since doing FVM-related crate maintainership and needs to be able to do releases (at least until we get more automation in place)

Also removed raulk given he isn't involved with the project currently.

Relevant since doing FVM-related crate maintainership and needs to be able to do releases (at least until we get more automation in place)

Also removed raulk given he isn't involved with the project currently.
@BigLep BigLep requested a review from a team as a code owner August 15, 2025 05:20
Copy link
Contributor

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

Access Changes
User lesnyrumcajs:
  - will have the permission to builtin-actors change from push to admin
  - will have the permission to ref-fvm change from maintain to admin
  - will gain admin permission to actors-utils
  - will gain admin permission to builtin-actors-bundler
  - will gain admin permission to fuzzing-fvm
  - will gain admin permission to fvm-wasm-instrument
  - will gain admin permission to fvm-workbench
  - will gain admin permission to wasm-tools
User raulk:
  - will lose admin permission to actors-utils
  - will have the permission to builtin-actors change from admin to push
  - will have the permission to builtin-actors-bundler change from admin to push
  - will have the permission to fuzzing-fvm change from admin to maintain
  - will lose admin permission to fvm-wasm-instrument
  - will lose admin permission to fvm-workbench
  - will have the permission to ref-fvm change from admin to push
  - will lose admin permission to wasm-tools

Copy link
Contributor

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

Terraform plans

filecoin-project

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create
  - destroy

Terraform will perform the following actions:

  # github_team_membership.this["fvm-crate-owners:lesnyrumcajs"] will be created
  + resource "github_team_membership" "this" {
      + etag     = (known after apply)
      + id       = (known after apply)
      + role     = "member"
      + team_id  = "5754561"
      + username = "LesnyRumcajs"
    }

  # github_team_membership.this["fvm-crate-owners:raulk"] will be destroyed
  # (because key ["fvm-crate-owners:raulk"] is not in for_each map)
  - resource "github_team_membership" "this" {
      - etag     = "W/\"5cfbea5ef7ee0012e88963c95b99daa7cd486a5ac4632367473020c2187d4d06\"" -> null
      - id       = "5754561:raulk" -> null
      - role     = "member" -> null
      - team_id  = "5754561" -> null
      - username = "raulk" -> null
    }

Plan: 1 to add, 0 to change, 1 to destroy.

@BigLep BigLep self-assigned this Aug 15, 2025
@BigLep BigLep requested a review from rvagg August 15, 2025 06:01
@rjan90 rjan90 merged commit 5bf6c54 into master Aug 15, 2025
6 checks passed
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.

2 participants