Skip to content

Conversation

@galargh
Copy link
Contributor

@galargh galargh commented Apr 21, 2025

Summary

Why do you need this?

What else do we need to know?

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

@galargh galargh requested review from a team as code owners April 21, 2025 11:06
@github-actions
Copy link
Contributor

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

Terraform plans

ipfs-examples

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_membership.this["web3-bot"] will be created
  + resource "github_membership" "this" {
      + etag     = (known after apply)
      + id       = (known after apply)
      + role     = "member"
      + username = "web3-bot"
    }

Plan: 1 to add, 0 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 web3-bot:
  - will join the organization as a member (remind them to accept the email invitation)

@galargh galargh merged commit 35f9e91 into master Apr 21, 2025
6 checks passed
@galargh galargh deleted the galargh-patch-3 branch April 21, 2025 11:08
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