Skip to content

[Initiative] Branch Naming Enforcement Workflow #1755

Open

Description

@ashleyshaw

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:

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)

Activity

  1. linear-code commented on Aug 11, 2026

    @linear-code
  2. github-actions commented on Aug 11, 2026

    @github-actions
    Contributor

    ✅ Template check passed after update. Thanks for fixing the issue body.

  3. github-actions commented on Aug 11, 2026

    @github-actions
    Contributor

    ⏱️ 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-11T10:34:03.397Z

    Maintained by project-meta-sync workflow.

  4. self-assigned this
    on Sep 8, 2026
  5. github-actions commented on Sep 8, 2026

    @github-actions
    Contributor

    ⚠️ Bare Labels Detected

    This issue has labels that are not in the canonical taxonomy:

    • migrate:area:ci
    • migrate:priority:important
    • migrate:status:needs-more-info
    • migrate:meta:needs-changelog
    • migrate:type:epic

    Valid Canonical Labels

    Please use labels with a prefix from the canonical taxonomy:

    • Type: type:bug, type:feature, type:task, type:documentation, etc.
    • Status: status:needs-triage, status:in-progress, status:done, etc.
    • Priority: priority:critical, priority:high, priority:normal, priority:low
    • Area: area:ci, area:docs, area:labels, area:security, etc.
    • Meta: meta:needs-changelog, meta:duplicate, meta:blocked, etc.

    For the complete list, see .github/labels.yml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Fields

Priority

None yet

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions