fix: exempt dependabot PRs from branch name validation

[ashleyshaw]

Summary

Adds exemption for dependabot and renovate PRs from branch name validation checks.

• Exempts and PR authors
• Skips validation for branches matching and patterns
• Allows automated dependency update PRs to merge without branch naming conflicts

Resolves

• Fixes PR build(deps): bump linkify-it and markdownlint #1864: build(deps): bump linkify-it and markdownlint
• Fixes PR build(deps): bump markdown-it, markdownlint and markdownlint-cli2 #1870: build(deps): bump markdown-it, markdownlint and markdownlint-cli2

Why

GitHub's dependabot creates branches with names like dependabot/npm_and_yarn/multi-{hash} which don't follow the LightSpeed branching strategy ({type}/{scope}-{title}). Since we cannot control dependabot's branch naming, we need to exempt it from validation to allow these critical dependency updates to merge automatically.

[coderabbitai]

Warning

Review limit reached

@ashleyshaw, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 19 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 2494dd50-c0fe-4c4f-a194-5929283544d1

📥 Commits

Reviewing files that changed from the base of the PR and between c5e1116 and f181f47.

📒 Files selected for processing (1)

• .github/workflows/branch-name-validation.yml

---

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]

❌ Branch Name Validation Failed

The branch name fix/dependabot-branch-validation-exemption 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.

[github-actions]

⏱️ Aging and SLA annotation

• Age: 0 day(s)
• SLA state: Within SLA
• Thresholds: warn at 7 days, breach at 14 days
• Last updated: 2026-08-12T21:58:20.868Z

Maintained by project-meta-sync workflow.

[github-actions]

⚠️ A merged PR reached develop without passing the template content guardrail.

Missing required section(s): Linked issues, Changelog, Global DoD checklist

This is a post-merge backstop for admin bypasses. Please review branch protection for develop.

[github-actions]

🔍 Reviewer Summary for PR #1933

CI Status: ❌ success
Files changed: 1
Risk Distribution: 1 critical, 0 high, 0 medium, 0 low

Recommendations

• ⚠️ 1 critical-risk file(s) modified (workflows, secrets)
• ⚠️ Security-sensitive files modified (review carefully)

---