Repository navigation
fix(ci): name the branch-protection job so the required check matches - #1239
Merged
Merged
Conversation
The org ruleset on beta requires the status check "branch-protection / check-branch". A reusable-workflow check is named "<caller job key> / <callee job>", 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 <noreply@anthropic.com>
remko48
approved these changes
Oct 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The org ruleset on
betarequires the status checkbranch-protection / check-branch. A reusable-workflow check is reported as<caller job key> / <callee job>, and this repo's caller job in.github/workflows/branch-protection.ymlwas keyedprotect, so the check ran green asprotect / check-branchwhile the required context never arrived.Result: every
development → betapromotion PR (currently #1026) staysBLOCKEDon "Expected — Waiting for status to be reported", even with an approval and all checks green.This PR renames the job key to
branch-protection, matching portaliq and thematiq. No behaviour change in the check itself.After merge
The sync-to-beta workflow updates #1026; its
check-branchrun then reports under the required name. The new head on #1026 needs a fresh approval.Test plan
branch-protection / check-branchas a passing required check🤖 Generated with Claude Code