fix(workflows): actually match main's required check name this time

[eleshar]

Linked issues

Relates to #2351, follow-up to #2363 which didn't actually fix the problem.

Changelog

Fixed

• fix(workflows): remove job name override breaking main's required status check #2363 removed a name: validate-release-branch override on the validate-release-branch job, on the theory that GitHub auto-prefixes check names with the workflow name. It doesn't for a plain job — confirmed via the GitHub API after fix(workflows): remove job name override breaking main's required status check #2363 merged, the check still reported as bare validate-release-branch, identical to before. Sets name: "Main Branch Guard / validate-release-branch" explicitly, matching the literal string main's branch protection requires.

Risk Assessment

Risk Level: Low

Potential Impact: Only changes the reported check-run name, no change to validation logic.

Mitigation Steps: Verified locally that the resulting YAML is valid before pushing.

How to Test / Test Plan

Confirm via the GitHub API that the check-run name on the next PR against main is exactly Main Branch Guard / validate-release-branch, and that #2351's mergeStateStatus clears to CLEAN.

Checklist (Global DoD / PR)

• Confirmed the previous attempt's failure via API before writing this fix
• YAML validity checked locally

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (5)

• main
• develop
• feature/*
• fix/*
• update/*

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro Plus

Run ID: 828fa0cf-460c-4171-a22e-56af5cd9b211

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Note

.coderabbit.yml has unrecognized properties

CodeRabbit is using all valid settings from your configuration. Unrecognized properties (listed below) have been ignored and may indicate typos or deprecated fields that can be removed.

⚠️ Parsing warnings (1)

Validation error: Unrecognized keys: "auto_labels", "auto_assign", "auto_review"

⚙️ Configuration instructions

• Please see the configuration documentation for more information.
• You can also validate your configuration using the online YAML validator.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Milestone Allocation

[github-actions]

❌ Branch Name Validation Failed

The branch name fix/main-branch-guard-job-name-v2 does not follow the LightSpeed branching strategy.

Required Format

{type}/{scope}-{short-title}

• type: one of the allowed prefixes (lowercase)
• scope: lowercase, hyphens only (no underscores or uppercase)
• title: lowercase, hyphens only (no underscores or uppercase)

Allowed Branch Types

feat, fix, hotfix, release, refactor, chore, docs, test, perf, ci, build, deps, security, revert, research, design, a11y, ux, i18n, ops, proto, ds, api, schema, telemetry, content, seo, config, migrate, qa, uat, audit, codex

Valid Examples

• ✓ feat/branch-naming-enforcement
• ✓ fix/validation-script-bug
• ✓ chore/update-dependencies
• ✓ docs/branching-strategy-guide
• ✓ hotfix/critical-security-patch

Invalid Examples

• ✗ claude/my-branch (type "claude" not allowed)
• ✗ Feature/MyBranch (uppercase not allowed)
• ✗ fix-bug (missing type prefix)
• ✗ feat/my_feature (underscores not allowed)
• ✗ feat/MyFeature (uppercase not allowed)

Solution

Rename your branch to follow the pattern and update the PR.

For more information, see docs/BRANCHING_STRATEGY.md.