Skip to content

Enforce PR labeling requirement - all PRs must have labels #2352

Closed

Description

@ashleyshaw

Overview

All PRs must have labels without exception. This is a governance requirement to maintain proper issue triage and tracking.

Current State

PR #2351 (v1.0.0 release) was created without labels, which violates this requirement.

Required Action

Implement automatic labeling or workflow enforcement to ensure:

  1. All PRs targeting develop must have at least one label from:

    • type:* labels (feature, bug, etc.)
    • area:* labels (ci, docs, security, etc.)
    • priority:* labels (critical, important, normal)
    • meta:* labels (needs-changelog, no-changelog, etc.)
  2. Workflow should either:

    • Auto-label PRs based on branch prefix and file changes, OR
    • Block PR merge if labels are missing, with clear guidance
  3. Release PRs (branch: release/* or hotfix/*) should auto-label with type:release

Related Files

  • .github/workflows/labeling-governance.yml - Current labeling workflow
  • .github/labels.yml - Label definitions (158 canonical labels)
  • .github/labeler.yml - Path-based labeling rules

Acceptance Criteria

  • Issue created to track requirement
  • Workflow enforcement implemented
  • All PRs (including this one) comply with labeling requirement
  • Clear error message when PR is unlabeled

Related to PR #2351 (v1.0.0 release)

Activity

  1. linear-code commented on Aug 26, 2026

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

    @github-actions
    Contributor

    ⚠️ This issue does not follow a required issue template.

    Missing required section(s): Definition of Ready (DoR), Definition of Done (DoD)

    The issue will remain open and flagged until the body is corrected.
    Please update the issue with one of the official templates:

    If this was opened by automation, update the automation to preserve the template sections before creating the issue.

  3. github-actions commented on Aug 26, 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-26T23:05:45.965Z

    Maintained by project-meta-sync workflow.

  4. self-assigned this
    on Aug 29, 2026
  5. github-actions commented on Aug 29, 2026

    @github-actions
    Contributor

    Milestone Allocation

    
    
  6. 10 remaining items

  7. added this to the v1.1 milestone on Sep 3, 2026
  8. 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:normal
    • migrate:status:needs-more-info
    • migrate:meta:needs-changelog
    • migrate:type:task

    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

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions