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

Terraform plans

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

Terraform will perform the following actions:

  # github_team_repository.this["Go Team:multicodec"] will be destroyed
  # (because key ["Go Team:multicodec"] is not in for_each map)
  - resource "github_team_repository" "this" {
      - etag       = "W/\"7feef9aadcb96926e4495165a8b5c77942401decee1a1322977c222f096de2c0\"" -> null
      - id         = "2210603:multicodec" -> null
      - permission = "push" -> null
      - repository = "multicodec" -> null
      - team_id    = "2210603" -> null
    }

  # github_team_repository.this["JavaScript Team:multicodec"] will be destroyed
  # (because key ["JavaScript Team:multicodec"] is not in for_each map)
  - resource "github_team_repository" "this" {
      - etag       = "W/\"7feef9aadcb96926e4495165a8b5c77942401decee1a1322977c222f096de2c0\"" -> null
      - id         = "2123131:multicodec" -> null
      - permission = "push" -> null
      - repository = "multicodec" -> null
      - team_id    = "2123131" -> null
    }

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

FYI, only members of github-mgmt stewards team can merge the PRs in this repo. Since there are 2 approves here already, I'm going to do it.

this seems like not the actually intended behavior and i'd like to limit this to protection of the main branch.

Push access means i can't directly make a PR to start a discussion. I don't think that's the intention and what you want for now is more limited approval for actually merging things.

It isn't sustainable to say we won't allow discussion / include any updated protocols for months at a time - the alternative is that people will continue allocating codecs that make sense without contributing them or having the discussion here.

@galargh could you help us with the settings to just protect merges into the main branch for now, then it's not so important who has branch access? I guess something similar to what's going on in go-car now might be appropriate and it looks like we have a bunch of settings to enable here to make that happen.

Alternatively, give me some pointers and I'll put up a PR.

I just enabled a more fine-grained configuration of branch protection rules in this repo.

Here's the current config for master protection of multicodecs:

Now you can modify them through a PR 🎉

Please also add back the Contributors group at least to be able to write to the repo

I think #67 gets us to where we want to be