add self as collaborator to go-delegated-routing

[willscott]

Have PRs, but can't tag reviewers.

Would make this as a PR I can tag reviewers against in this repo as requested by stewards, but can't per #30

[github-actions]

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

Terraform plans

ipfs

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

Terraform will perform the following actions:

  # github_repository_collaborator.this["go-delegated-routing:willscott"] will be created
  + resource "github_repository_collaborator" "this" {
      + id                          = (known after apply)
      + invitation_id               = (known after apply)
      + permission                  = "push"
      + permission_diff_suppression = false
      + repository                  = "go-delegated-routing"
      + username                    = "willscott"
    }

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

[galargh]

I was wondering, can we add go-delegated-routing to Repos - Go instead? I can move forward with #32 if that's OK.

Also, do you happen to know why we have both Repos - Go and Merge - Go team? I suspect that it wasn't the case when they were being created but right now it seems that Merge - Go is a subset of Repos - Go so maybe we could consolidate the two.

[galargh]

Have PRs, but can't tag reviewers.

Oh wait, that we can easily broaden. We could give everyone in the org triage access here which would allow requesting reviews - #33

[willscott]

Fine with #32 instead

[willscott]

Merge is a relatively small number of pretty trusted people. Those people should generally be okay to merge to e.g. protected main branches / cut releases. I would also assert that those people should have the trust to update repo permissions and add collaborators

[galargh]

Closing since I merged #32

Merge is a relatively small number of pretty trusted people. Those people should generally be okay to merge to e.g. protected main branches / cut releases. I would also assert that those people should have the trust to update repo permissions and add collaborators

Got it. Just wondered because in practice Merge - Go has no more access to any repo than Repos - Go