Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add bethanymarz as a member #81

Open
wants to merge 11 commits into
base: master
Choose a base branch
from
Open

Conversation

bethanymarz
Copy link

Summary
Adding bethanymarz as an org member

Why do you need this?
Bethany is working with Shipyard (https://ipshipyard.com/) and having basic org membership should help her with some tooling around ecosystem analysis.

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

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

Summary
Adding bethanymarz as an org member

Why do you need this?
Bethany is working with Shipyard (https://ipshipyard.com/) and having basic org membership should help her with some tooling around ecosystem analysis.

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
@bethanymarz bethanymarz requested review from a team as code owners April 9, 2024 20:50
Copy link
Contributor

github-actions bot commented Apr 9, 2024

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

Terraform plans

ipld

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

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

Copy link
Contributor

github-actions bot commented Apr 9, 2024

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

Access Changes
User bethanymarz:
  - will join the organization as a [object Object] (remind them to accept the email invitation)

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.

None yet

1 participant