Skip to content

Conversation

@darobin
Copy link
Contributor

@darobin darobin commented May 15, 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

@darobin darobin requested a review from a team as a code owner May 15, 2025 13:42
@darobin darobin requested review from a team and laurentsenta May 15, 2025 13:42
@github-actions
Copy link
Contributor

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

Access Changes
User darobin:
  - will gain push permission to ipfs-blog

@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

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["ipfs-blog:darobin"] will be created
  + resource "github_repository_collaborator" "this" {
      + id                          = (known after apply)
      + invitation_id               = (known after apply)
      + permission                  = "push"
      + permission_diff_suppression = false
      + repository                  = "ipfs-blog"
      + username                    = "darobin"
    }

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

@galargh galargh merged commit 8a6ea31 into ipfs:master May 18, 2025
6 checks passed
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