From 1ad6e516c56aca85672b545034344a394bbd2d93 Mon Sep 17 00:00:00 2001 From: Elior Erez Date: Fri, 31 Jul 2026 12:10:39 -0400 Subject: [PATCH] Require all 3 osac e2e install checks on main osac's own CI (vmaas/bmaas/caas full-install) has been live and passing on real PRs for a while now, but repo_osac's required_status_checks was left empty from before that CI existed -- meaning a PR could currently merge into osac:main with every check failing. Matches the pattern already enforced on fulfillment-service/osac-operator/osac-aap (one required check each), but requires all 3 e2e flavors here since this is now the repo everything actually merges into. --- repositories.tf | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/repositories.tf b/repositories.tf index dbca4af..4d51f7e 100644 --- a/repositories.tf +++ b/repositories.tf @@ -142,10 +142,15 @@ module "repo_osac" { } ] required_approvals = null - # No required_status_checks yet -- the mono-repo's CI doesn't exist until - # content is merged in. Add checks here once that CI is built, following the - # same pattern as repo_fulfillment_service/repo_cloudkit_operator above. - required_status_checks = [] + # osac's own CI (all 3 e2e install flavors) is live and has been passing on + # real PRs for a while now -- require all 3, not just vmaas like the + # pre-merge component repos below, since this is now the repo everything + # actually merges into. + required_status_checks = [ + { context = "e2e-vmaas-full-install / e2e", integration_id = 15368 }, + { context = "e2e-bmaas-full-install / e2e", integration_id = 15368 }, + { context = "e2e-caas-full-install / e2e", integration_id = 15368 }, + ] # Preserve subtree-merge history/blame going forward -- squash-merging on the # mono-repo would collapse that history for every commit after cutover, so # it's disabled at the GitHub level, not just by convention.