Skip to content

Conversation

@hsanjuan
Copy link
Contributor

@hsanjuan hsanjuan commented Jan 14, 2026

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

@github-actions
Copy link
Contributor

github-actions bot commented Jan 14, 2026

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

Access Changes
User achingbrain:
  - will have the permission to ipfs-deploy-action change from pull to push
  - will gain push permission to kubo
User aschmahmann:
  - will have the permission to ipfs-deploy-action change from pull to push
  - will gain push permission to kubo
User cewood:
  - will have the permission to ipfs-deploy-action change from pull to push
  - will gain push permission to kubo
User gammazero:
  - will have the permission to ipfs-deploy-action change from pull to push
  - will gain push permission to kubo
User guillaumemichel:
  - will have the permission to ipfs-deploy-action change from pull to push
  - will gain push permission to kubo
User hsanjuan:
  - will have the permission to ipfs-deploy-action change from pull to push
  - will gain push permission to kubo
User lidel:
  - will have the permission to ipfs-deploy-action change from pull to push
  - will gain push permission to kubo
User ns4plabs:
  - will have the permission to ipfs-deploy-action change from pull to push

@github-actions
Copy link
Contributor

github-actions bot commented Jan 14, 2026

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_team_repository.this["engineering:ipfs-deploy-action"] will be updated in-place
  ~ resource "github_team_repository" "this" {
        id         = "10925582:ipfs-deploy-action"
      ~ permission = "pull" -> "push"
        # (3 unchanged attributes hidden)
    }

  # github_team_repository.this["engineering:kubo"] will be created
  + resource "github_team_repository" "this" {
      + etag       = (known after apply)
      + id         = (known after apply)
      + permission = "push"
      + repository = "kubo"
      + team_id    = "10925582"
    }

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

@aschmahmann
Copy link
Contributor

@hsanjuan I'm fine with this, but this is for updating the ipfs-deploy-action permissions rather than ipshipyard/kubo. If you want both changed can you update the PR?

@hsanjuan
Copy link
Contributor Author

Sorry, I edited directly on github and not sure how I ended up doing it wrong.

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.

3 participants