Skip to content

ci: rename branch-protection caller job id to branch-protection - #116

Merged
rubenvdlinde merged 1 commit into
developmentfrom
ci/branch-protection-job-id
Aug 4, 2026
Merged

ci: rename branch-protection caller job id to branch-protection#116
rubenvdlinde merged 1 commit into
developmentfrom
ci/branch-protection-job-id

Conversation

@rubenvdlinde

Copy link
Copy Markdown
Contributor

GitHub names a reusable-workflow status context <caller-job-id> / <called-job-name>.

development is the head branch of the development -> beta release PRs, so development's
tip is what decides the context name on those PRs
— not beta's. With a caller job id other
than branch-protection, the org ruleset requirement branch-protection / check-branch never
reported on any release PR, leaving them permanently BLOCKED.

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.

…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`. development is the head branch for the
`development -> beta` release PRs, so its tip decides the context name on those PRs.
@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/openbuild @ d054d26

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
build
composer ✅ 101/101
npm ✅ 654/654
PHPUnit
Newman ⏭️
Playwright ⏭️

Quality workflow — 2026-08-04 06:21 UTC

Download the full PDF report from the workflow artifacts.

@rubenvdlinde
rubenvdlinde merged commit 6d83d23 into development Aug 4, 2026
33 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant