Skip to content

Labels

Labels

  • attention/decision

    A human product, design, or technical decision is required before continuing.
  • attention/human

    Human involvement is required because automation cannot safely proceed alone.
  • good first issue

    Suitable entry point for a new contributor.
  • help wanted

    Additional contribution or ownership is actively welcome.
  • issue/confirmed

    Problem validated with evidence; does not imply priority, scheduling, or approval to implement.
  • issue/investigating

    Actively being investigated by the assignee; coordinate before starting overlapping work.
  • issue/needs-info

    Awaiting specific information from the reporter or requester before work can continue.
  • issue/needs-mre

    Needs a minimal reproducible example with steps, environment, and expected vs. actual behavior.
  • issue/needs-triage

    Needs maintainer assessment, prioritization, or routing before work can proceed.
  • issue/ready

    Approved and scoped for implementation, with acceptance criteria and no unresolved blockers.
  • merge/auto

    Safe to merge automatically once required gates pass, after review approval.
  • merge/hold

    Technically ready, but intentionally blocked from merging.
  • question

    Primarily a question or request for clarification.
  • resolution/by-design

    The reported behavior is intentional and working as designed.
  • resolution/duplicate

    The same problem, request, or discussion is already tracked elsewhere.
  • resolution/invalid

    The premise, report, or request is invalid or not applicable.
  • resolution/superseded

    Replaced by a newer issue, decision, design, or implementation direction.
  • resolution/wontfix

    Valid request or issue that has intentionally been declined.
  • risk/high

    High-impact, sensitive, or difficult-to-reverse change.
  • risk/low

    Low-impact and easy-to-reverse change; lightweight review is sufficient.
  • risk/medium

    Moderate-impact change requiring deliberate review.
  • stacked

    Part of a stacked PR chain and should be reviewed in dependency context.
  • type/chore

    Maintenance, tooling, dependencies, or repository housekeeping.
  • type/cleanup

    Removes dead code, deprecated paths, lint debt, or obsolete artifacts.
  • type/contract

    Defines or changes an API, interface, schema, IPC, protocol, or boundary shape.
  • type/data

    Defines or changes data entities, value objects, domain data, or related invariants.
  • type/dependency

    Updates dependencies, versions, lockfiles, or package relationships.
  • type/feature

    Introduces a new capability or meaningful user-facing behavior.
  • type/fix

    Corrects broken or unintended existing behavior.
  • type/flag

    Adds, changes, flips, or removes release, control, permission, or experiment flags.