Uh oh!
There was an error while loading. Please reload this page.
fix(workflows): remove job name override breaking main's required status check - #2363
Conversation
…tus check main's branch protection requires the check "Main Branch Guard / validate-release-branch" (GitHub's default <workflow name> / <job id> format), but the job explicitly overrode its display name to just "validate-release-branch" — a context string that can never match what branch protection expects. This permanently blocked every release PR from becoming mergeable to main, including #2351, even after the job itself passed and the PR was approved. Removing the override lets GitHub report the check under its default name, matching what's already configured in branch protection.
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (5)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Note
|
Tick the box to add this pull request to the merge queue (same as
|
Uh oh!
There was an error while loading. Please reload this page.
Milestone Allocation |
Linked issues
Relates to #2351. This is what was actually blocking it from becoming mergeable.
Changelog
Fixed
main-branch-guard.yml'svalidate-release-branchjob explicitly overrode its display name tovalidate-release-branch, but main's branch protection requires the checkMain Branch Guard / validate-release-branch(GitHub's default<workflow name> / <job id>format). The two strings can never match, so this permanently blocked every release PR tomainfrom becoming mergeable, regardless of approval or the job's own pass/fail result. Removed the override.Risk Assessment
Risk Level: Low
Potential Impact: Only affects how this one check's name is reported to branch protection; no change to what the job actually validates.
Mitigation Steps: Confirmed the job's validation logic is untouched — only the
name:line was removed.How to Test / Test Plan
Once merged, #2351's
mergeStateStatusshould move fromBLOCKEDtoCLEAN(already approved, already passing its one required check by content — just reported under the wrong name).Checklist (Global DoD / PR)
Main Branch Guard / validate-release-branchand the reported context was the mismatchedvalidate-release-branch