ci: rename branch-protection caller job id to branch-protection - #114
Open
rubenvdlinde wants to merge 1 commit into
Open
ci: rename branch-protection caller job id to branch-protection#114rubenvdlinde wants to merge 1 commit into
branch-protection#114rubenvdlinde wants to merge 1 commit into
Conversation
…ion` GitHub names a reusable-workflow status context `<caller-job-id> / <called-job-name>`, so this caller reported as `check / 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.
Contributor
Quality Report — ConductionNL/openbuild @
|
| Check | PHP | Vue | Security | License | Tests |
|---|---|---|---|---|---|
| lint | ✅ | ||||
| phpcs | ❌ | ||||
| phpmd | ✅ | ||||
| psalm | ✅ | ||||
| phpstan | ✅ | ||||
| phpmetrics | ✅ | ||||
| eslint | ✅ | ||||
| stylelint | ✅ | ||||
| build | ✅ | ||||
| composer | ❌ | ✅ 100/100 | |||
| npm | ✅ | ✅ 389/389 | |||
| PHPUnit | ⏭️ | ||||
| Newman | ⏭️ | ||||
| Playwright | ⏭️ |
Quality workflow — 2026-08-04 06:17 UTC
Download the full PDF report from the workflow artifacts.
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
1 participant
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.
GitHub names a reusable-workflow status context
<caller-job-id> / <called-job-name>.This repo's caller job id was not
branch-protection, so the shared branch-protectionworkflow reported under the wrong context name. The org rulesets (
Main Branch Protectionid 14128365,
Beta Branch Protectionid 14128357) require exactly:No name match means the required context never reported at all — not as a failure, as
nothing. The PR sits at
BLOCKEDforever, and the absence of the check is visually identical tothe check merely not having finished yet. That is the whole defect: a check's absence looks
exactly like its success is still pending.
This renames the caller job id so the context matches. It does not change what is required and
does not touch any ruleset or branch protection — that is a governance decision, not a code
one.
Irony worth recording: this PR itself has to be admin-merged, because the defect it fixes is
precisely what makes the required context unreportable on the current tip.