Skip to content

Conversation

@guillaumemichel
Copy link
Contributor

Summary

Giving myself write access to ipshipyard.com

Why do you need this?

Publish/draft reprovide sweep blogpost

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

Access needed to publish reprovide sweep blogpost
@github-actions
Copy link
Contributor

github-actions bot commented Oct 2, 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

Terraform will perform the following actions:

  # github_repository_collaborator.this["ipshipyard.com:guillaumemichel"] will be created
  + resource "github_repository_collaborator" "this" {
      + id                          = (known after apply)
      + invitation_id               = (known after apply)
      + permission                  = "push"
      + permission_diff_suppression = false
      + repository                  = "ipshipyard.com"
      + username                    = "guillaumemichel"
    }

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

@github-actions
Copy link
Contributor

github-actions bot commented Oct 2, 2025

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

Access Changes
User guillaumemichel:
  - will gain push permission to ipshipyard.com

@galargh galargh merged commit ec555c9 into ipshipyard:master Oct 5, 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