From 6af83f47e6a5d5af8b2c9453f95929b167564f20 Mon Sep 17 00:00:00 2001 From: WilcoLouwerse Date: Tue, 6 Oct 2026 15:52:18 +0200 Subject: [PATCH] fix(ci): name the branch-protection job so the required check matches MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The org ruleset on beta requires the status check "branch-protection / check-branch". A reusable-workflow check is named " / ", and this repo's caller job was keyed `protect`, so the check reported as "protect / check-branch" and the required context never arrived. Every development -> beta promotion PR stayed blocked on "Expected — Waiting for status to be reported". Rename the job key to `branch-protection`, matching portaliq and thematiq. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/branch-protection.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/branch-protection.yml b/.github/workflows/branch-protection.yml index d3e40cad8..3d7f6785d 100644 --- a/.github/workflows/branch-protection.yml +++ b/.github/workflows/branch-protection.yml @@ -7,7 +7,7 @@ on: - beta jobs: - protect: + branch-protection: # The callee's `check-branch` job is a single bash comparison of # `github.base_ref` against `github.head_ref` — no checkout, no network, no # API call. It needs nothing, so it gets nothing. `{}` is an explicit empty