[BUG]: Delete Repository In another Org after xfer

[match-caseydaniell]

Expected Behavior

We transferred a repository from Org A to a new Org Z (both in our GitHub Enterprise) .

After performing the transfer I removed the Terraform block that created and controlled the repository in the TF code controlling Org A, but left the code in the TF code controlling Org Z.

Actual Behavior

My expectation is that only the state files would get cleaned up, and no actual repo removals would occur as the repository existed in Org Z now.

Terraform Version

required_version = "> 1.12"
required_providers {
github = {
source = "integrations/github"
version = "> 6.6.0"
}

Affected Resource(s)

• github_repository

Terraform Configuration Files

module "RepoName" {
  source      = "../modules/org_repository"
  name        = "RepoName"
  description = ""
  topics = [
    "tsql"
  ]
  protected_branches_ruleset = local.default_protected_branches_ruleset.main
  admin-members = [
    local.users.redactedUser1,
    local.users.redactedUser2
  ]
  write-members = distinct(concat(
    local.global-users.write-members,
    [
      local.users.redacted-user3
      local.users.redacted-user4,
      .....
      local.users.recacted-userX,
    ]
  ))
}

Steps to Reproduce

Sequence of events

1. Created a new github.com// repo via Terraform https://github.com//github-terraform-repository
2. Manually deleted github.com// repo leaving the terraform state files as they were. This is what controls repos / teams / etc in github.com/
3. Changed ownership of github.com// from to which transferred the repo over to
4. I realized the terraform code controlling was breaking as I didn't remove from https://github.com//github-terraform-repository so I removed from the org's terraform and pushed through a change, which I expected to only clean up local Terraform state files for
5. The removal of in https://github.com//github-terraform-repository via https://github.com//github-terraform-repository/actions/runs/###### reached across orgs and deleted it from the github.com/ org, which is unexpected.

PAT used for this DOES have access to both orgs, however, I didn't expect a change in terraform in one org to reach across org boundaries find the repo in it's "new home" and remove it from there.

Debug Output

Panic Output

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[deiga]

I can understand that this is a frustrating situation.
I assume this happened exactly because your PAT had access to both ORGs and the GH API does redirects when accessing renames or transferred repos.

In general you should always use a removed block, when you want to ensure that terraform only clears state without API calls