Skip to content

Conversation

@galargh
Copy link
Contributor

@galargh galargh commented Dec 8, 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 December 8, 2025 21:22
@github-actions
Copy link
Contributor

github-actions bot commented Dec 8, 2025

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

Access Changes
There will be no access changes

@github-actions
Copy link
Contributor

github-actions bot commented Dec 8, 2025

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

Terraform plans

multiformats

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # github_branch_protection.this["github-mgmt:master"] will be updated in-place
  ~ resource "github_branch_protection" "this" {
        id                              = "BPR_kwDOG2nBTM4BejP_"
        # (10 unchanged attributes hidden)

      ~ required_pull_request_reviews {
          ~ required_approving_review_count = 2 -> 1
            # (6 unchanged attributes hidden)
        }

        # (1 unchanged block hidden)
    }

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

@galargh galargh merged commit 30e4cc0 into master Dec 8, 2025
6 checks passed
@galargh galargh deleted the galargh-patch-1 branch December 8, 2025 22:20
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