Skip to content

Conversation

@achingbrain
Copy link
Contributor

Summary

Adds me and engineering to the www-helia-io repo

Why do you need this?

To allow configuring and making changes

What else do we need to know?

n/a

DRI: myself

Reviewer's Checklist

  • It is clear where the request is coming from (if unsure, ask)
  • All the automated checks passed
  • The YAML changes reflect the summary of the request
  • The Terraform plan posted as a comment reflects the summary of the request

@github-actions
Copy link
Contributor

github-actions bot commented Sep 15, 2025

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

Terraform plans

ipshipyard

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

Terraform will perform the following actions:

  # github_repository.this["www-helia-io"] will be updated in-place
  ~ resource "github_repository" "this" {
        id                          = "www-helia-io"
        name                        = "www-helia-io"
        # (33 unchanged attributes hidden)

      ~ security_and_analysis {

          ~ secret_scanning {
              ~ status = "disabled" -> "enabled"
            }

          ~ secret_scanning_push_protection {
              ~ status = "disabled" -> "enabled"
            }
        }

        # (1 unchanged block hidden)
    }

  # github_repository_collaborator.this["go-ds-crdt:web3-bot"] 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-ds-crdt"
      + username                    = "web3-bot"
    }

  # github_repository_collaborator.this["www-helia-io:achingbrain"] will be created
  + resource "github_repository_collaborator" "this" {
      + id                          = (known after apply)
      + invitation_id               = (known after apply)
      + permission                  = "admin"
      + permission_diff_suppression = false
      + repository                  = "www-helia-io"
      + username                    = "achingbrain"
    }

  # github_repository_collaborator.this["www-helia-io:engineering"] will be created
  + resource "github_repository_collaborator" "this" {
      + id                          = (known after apply)
      + invitation_id               = (known after apply)
      + permission                  = "push"
      + permission_diff_suppression = false
      + repository                  = "www-helia-io"
      + username                    = "engineering"
    }

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

@github-actions
Copy link
Contributor

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

Access Changes
User achingbrain:
  - will gain admin permission to www-helia-io
User web3-bot:
  - will gain push permission to go-ds-crdt
User engineering:
  - will gain push permission to www-helia-io

@aschmahmann aschmahmann merged commit ad34724 into ipshipyard:master Sep 15, 2025
6 checks passed
@achingbrain achingbrain deleted the patch-1 branch September 16, 2025 06:31
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