filecoin-project / github-mgmt

0 stars 6 forks source link

fevm-contract-tests #62

Closed rvagg closed 2 months ago

rvagg commented 2 months ago

Mainly I just want access to this repo, to at least push, but since nobody else is caring for it, admin would be good to take care of some things. I've added lotus-maintainers and FIL-B here for now, that's my best guess for who should "own" it.

github-actions[bot] commented 2 months ago

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

Access Changes ``` User aarshkshah1992: - will gain admin permission to fevm-contract-tests User arajasek: - will lose push permission to fevm-contract-tests User biglep: - will gain admin permission to fevm-contract-tests User jennijuju: - will gain admin permission to fevm-contract-tests User kubuxu: - will have the permission to fevm-contract-tests change from push to admin User longfeiwan9: - will gain admin permission to fevm-contract-tests User maciejwitowski: - will lose push permission to fevm-contract-tests User magik6k: - will gain admin permission to fevm-contract-tests User masih: - will gain admin permission to fevm-contract-tests User rjan90: - will gain admin permission to fevm-contract-tests User rk-rishikesh: - will gain admin permission to fevm-contract-tests User rvagg: - will gain admin permission to fevm-contract-tests User snissn: - will gain admin permission to fevm-contract-tests User stebalien: - will have the permission to fevm-contract-tests change from push to admin User tippyflitsuk: - will gain admin permission to fevm-contract-tests User trruckerfling: - will gain admin permission to fevm-contract-tests User xbalbinus: - will gain admin permission to fevm-contract-tests User xors-eng: - will gain admin permission to fevm-contract-tests User zenground0: - will have the permission to fevm-contract-tests change from push to admin ```
github-actions[bot] commented 2 months ago

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_repository_collaborator.this["fevm-contract-tests:arajasek"] will be destroyed # (because key ["fevm-contract-tests:arajasek"] is not in for_each map) - resource "github_repository_collaborator" "this" { - id = "fevm-contract-tests:arajasek" -> null - permission = "push" -> null - repository = "fevm-contract-tests" -> null - username = "arajasek" -> null } # github_repository_collaborator.this["fevm-contract-tests:maciejwitowski"] will be destroyed # (because key ["fevm-contract-tests:maciejwitowski"] is not in for_each map) - resource "github_repository_collaborator" "this" { - id = "fevm-contract-tests:maciejwitowski" -> null - permission = "push" -> null - repository = "fevm-contract-tests" -> null - username = "maciejwitowski" -> null } # github_team_repository.this["fil-b:fevm-contract-tests"] will be created + resource "github_team_repository" "this" { + etag = (known after apply) + id = (known after apply) + permission = "admin" + repository = "fevm-contract-tests" + team_id = "10353148" } # github_team_repository.this["lotus-maintainers:fevm-contract-tests"] will be created + resource "github_team_repository" "this" { + etag = (known after apply) + id = (known after apply) + permission = "admin" + repository = "fevm-contract-tests" + team_id = "4890221" } Plan: 2 to add, 0 to change, 2 to destroy. ```