From b6367c016bff7749b57322cb1e70972a3359664c Mon Sep 17 00:00:00 2001 From: Ruben van der Linde Date: Tue, 4 Aug 2026 08:06:58 +0200 Subject: [PATCH] ci: rename branch-protection caller job id `protect` -> `branch-protection` GitHub names a reusable-workflow status context ` / `, so this caller reported as `protect / check-branch` while the org ruleset requires `branch-protection / check-branch`. The required context never reported at all, leaving PRs to main/beta permanently BLOCKED. --- .github/workflows/branch-protection.yml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/.github/workflows/branch-protection.yml b/.github/workflows/branch-protection.yml index 67cdd608f..dc76f647f 100644 --- a/.github/workflows/branch-protection.yml +++ b/.github/workflows/branch-protection.yml @@ -5,6 +5,11 @@ on: branches: [main, beta] jobs: - protect: + # Job id must stay `branch-protection` so the check reports as + # `branch-protection / check-branch`, which is the context name the org + # ruleset requires. GitHub names a reusable-workflow context + # ` / `, so renaming this job silently + # detaches the required status check and leaves PRs permanently pending. + branch-protection: uses: ConductionNL/.github/.github/workflows/branch-protection.yml@main secrets: inherit