Repository navigation
Closed
Labels
area:buildsmigrate:area:ciBuild and CI pipelinesBuild and CI pipelinesmigrate:priority:importantMust-do high priorityMust-do high prioritymigrate:type:taskTask or to-doTask or to-dopriority:importanttype:task
Description
Component: GitHub Actions Validation Workflow
Parent Issue: #1755
Objective: Create GitHub Actions workflow for PR validation of branch names
Status: ✅ COMPLETED (Phase 1-3, 2026-08-22)
Deliverable: PR #2302 — Unified validators and agent branch guidance
Summary of Completed Work
This issue was completed as part of the unified Phase 1-3 implementation of branch naming enforcement:
Phase 1 (Validators):
- ✅ Created unified
.github/scripts/validation/validate-branch-name.cjs - ✅ Implemented strict
{type}/{scope}-{short-title}pattern validation - ✅ All 38 unit tests passing
Phase 2 (Agent Guidance & Workflow):
- ✅ Integrated branch validation into release agent pre-creation validation
- ✅ Added validation to 7-layer safety gates (Gate 1 pre-flight checks)
- ✅ Created workflow error messages with helpful guidance
Phase 3 (Discoverability & Documentation):
- ✅ Created quick reference guide:
docs/QUICK_REFERENCE_BRANCH_NAMING.md - ✅ Expanded CLAUDE.md with Before Every Push validation checklist
- ✅ Expanded AGENTS.md with Branch Governance section (120+ lines, 31 prefixes with examples)
- ✅ Added branch naming sections to all 19 portable agent AGENT.md files
- ✅ Created portable instructions:
instructions/branch-naming.instructions.md
Workflow Behavior:
- ✅ Validates branch name on PR creation/update
- ✅ Blocks merge if branch name is invalid
- ✅ Posts helpful comment with branching strategy link
- ✅ Supports all 31 branch prefixes
- ✅ Rejects forbidden prefixes (claude/, copilot/, openai/)
Acceptance Criteria:
- ✅ Workflow runs on pull_request event
- ✅ Validates all 31 allowed types
- ✅ Blocks merge on invalid branch names
- ✅ Posts actionable error comments
- ✅ No false positives/negatives
Documentation:
- ✅ Branch naming pattern documented in 40+ files
- ✅ Quick reference guide for developers
- ✅ Comprehensive setup instructions
- ✅ Portable reusable guidelines
- ✅ Cross-referenced throughout codebase
Effort: 3 hours
Definition of Ready (DoR)
- Clear problem statement and expected outcome
- Acceptance criteria defined
- Related issues/dependencies identified
- Required resources/approvals listed
Definition of Done (DoD)
- All acceptance criteria met
- Workflow tested and validated
- Error messages helpful and actionable
- Documentation comprehensive
- Changes merged in PR refactor(validation): P1-P2 - Unified validators and agent branch guidance #2302 (50 files, 893 additions)
- Stakeholders notified via project documentation
Metadata
Metadata
Assignees
Labels
area:buildsmigrate:area:ciBuild and CI pipelinesBuild and CI pipelinesmigrate:priority:importantMust-do high priorityMust-do high prioritymigrate:type:taskTask or to-doTask or to-dopriority:importanttype:task
Type
Fields
Priority
None yet
Activity
linear-code commentedon Aug 11, 2026
LS-2463
github-actions commentedon Aug 11, 2026
✅ Template check passed after update. Thanks for fixing the issue body.
github-actions commentedon Aug 11, 2026
⏱️ Aging and SLA annotation
Maintained by project-meta-sync workflow.
feat: Branch naming enforcement system (Phases 2-5) (#1781)
feat: Branch naming enforcement system (Phases 2-5) (#1781)
github-actions commentedon Sep 8, 2026
This issue has labels that are not in the canonical taxonomy:
migrate:area:cimigrate:priority:importantmigrate:type:taskValid Canonical Labels
Please use labels with a prefix from the canonical taxonomy:
type:bug,type:feature,type:task,type:documentation, etc.status:needs-triage,status:in-progress,status:done, etc.priority:critical,priority:high,priority:normal,priority:lowarea:ci,area:docs,area:labels,area:security, etc.meta:needs-changelog,meta:duplicate,meta:blocked, etc.For the complete list, see .github/labels.yml.