From bc3280bde1f84b40091499d97769d196219ba991 Mon Sep 17 00:00:00 2001 From: Elior Erez Date: Fri, 31 Jul 2026 21:39:22 -0400 Subject: [PATCH] Lock osac-installer ahead of its mono-repo merge Same lock_branch pattern already applied to fulfillment-service/ osac-operator/osac-aap/bare-metal-fulfillment-operator ahead of their own OSAC-1732 merges. The branch has already been locked directly via the GitHub API as an immediate stopgap; this PR makes it durable against Terraform's own ~4h auto-apply cycle. --- repositories.tf | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/repositories.tf b/repositories.tf index 14ab536..9187e7c 100644 --- a/repositories.tf +++ b/repositories.tf @@ -267,6 +267,11 @@ module "repo_osac_installer" { ruleset_bypass_team_ids = [github_team.all["wg-infra"].id] push_allowances = ["/openshift-merge-robot", "osac-project/wg-infra", "osac-project/org-admins"] environments = [{ name = "e2e-test" }] + # Frozen ahead of its merge into the osac mono-repo -- same pattern as + # fulfillment-service/osac-operator/osac-aap/bare-metal-fulfillment-operator. + # A one-off `gh api` toggle alone reverts on the next Terraform apply cycle + # without this. + lock_branch = true } module "repo_enhancement_proposals" {