Merge pull request from ictsc/master

[SouJimmy]

Add member to production

[github-actions]

Terraform Plan

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

Terraform will perform the following actions:

  # github_membership.member["dice-2004"] will be destroyed
  # (because key ["dice-2004"] is not in for_each map)
  - resource "github_membership" "member" {
      - etag     = "W/\"5d482a092d3ebe2317fee466753bf6933b18a1875599ac0ca6a8897d48cf00c1\"" -> null
      - id       = "ictsc:dice-2004" -> null
      - role     = "member" -> null
      - username = "dice-2004" -> null
    }

  # github_membership.member["kotokaze"] will be created
  + resource "github_membership" "member" {
      + etag     = (known after apply)
      + id       = (known after apply)
      + role     = "member"
      + username = "kotokaze"
    }

  # github_team_members.team_member["ictsc2026"] will be updated in-place
  ~ resource "github_team_members" "team_member" {
        id      = "17549702"
        # (2 unchanged attributes hidden)

      - members {
          - role     = "member" -> null
          - username = "dice-2004" -> null
        }

        # (40 unchanged blocks hidden)
    }

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

─────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't
guarantee to take exactly these actions if you run "terraform apply" now.