Repository navigation
Open
Labels
area:buildsmeta:needs-changelogmigrate:area:ciBuild and CI pipelinesBuild and CI pipelinesmigrate:meta:needs-changelogRequires a changelog entry before mergeRequires a changelog entry before mergemigrate:priority:importantMust-do high priorityMust-do high prioritymigrate:type:epicLarge multi-scope initiativeLarge multi-scope initiativepriority:importanttype:epic
Description
Initiative: Implement automated workflow to enforce strict branch naming conventions
Objective: Two-layer enforcement system (pre-commit hook + PR validation workflow) to eliminate manual validation drift
Linked Project: .github/projects/active/branch-naming-enforcement-2026-08-11/
Key Documents:
- SPEC.md — Detailed requirements
- RFC.md — Design decisions
- PLANNING.md — Execution plan
Child Issues:
- #TBD [Phase 2.1] Create validation script
- #TBD [Phase 2.2] Write unit tests for validation script
- #TBD [Phase 3.1] Create pre-commit hook
- #TBD [Phase 3.2–3.3] Setup command & multi-platform testing
- #TBD [Phase 4.1–4.2] GitHub Actions workflow & testing
- #TBD [Phase 5.1–5.3] Documentation (setup guide & troubleshooting)
- #TBD [Phase 6] Team rollout, deployment & monitoring
Related: Addresses branch naming violations in the repository
Status: 🚀 Ready for execution (2026-08-12)
Definition of Ready (DoR)
- Epic vision and scope clearly defined
- Success criteria and measurable outcomes documented
- High-level tasks/stories identified
- Dependencies and risks mapped
- Timeline and resource estimates provided
- Stakeholder alignment confirmed
Epic Owner / Sponsor
Sponsor/Owner: [Who is driving this epic]
Success Owner: [Who validates completion]
Success Criteria
- All Phase milestones achieved
- Stakeholder sign-off obtained
- Team capacity and velocity met targets
Definition of Done (DoD)
- All child issues/stories completed
- Epic acceptance criteria met
- Epic documentation and summary updated
- Release notes and announcement prepared
- Post-launch monitoring and support plan in place
- Retrospective completed (if applicable)
Metadata
Metadata
Assignees
Labels
area:buildsmeta:needs-changelogmigrate:area:ciBuild and CI pipelinesBuild and CI pipelinesmigrate:meta:needs-changelogRequires a changelog entry before mergeRequires a changelog entry before mergemigrate:priority:importantMust-do high priorityMust-do high prioritymigrate:type:epicLarge multi-scope initiativeLarge multi-scope initiativepriority:importanttype:epic
Type
Fields
Priority
None yet
Activity
linear-code commentedon Aug 11, 2026
LS-2458
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 Initiative — Phase 1 Planning & Speci…
github-actions commentedon Sep 8, 2026
This issue has labels that are not in the canonical taxonomy:
migrate:area:cimigrate:priority:importantmigrate:status:needs-more-infomigrate:meta:needs-changelogmigrate:type:epicValid 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.