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.
  • 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/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/fix

    Corrects broken or unintended existing behavior.
  • type/flag

    Adds, changes, flips, or removes release, control, permission, or experiment flags.
  • type/implementation

    Implements business or system behavior against an established shape.
  • type/integration

    Connects modules, services, adapters, dependency injection, or end-to-end flows.
  • type/migration

    Performs schema migration, backfill, data move, or config-format upgrade.
  • type/observability

    Adds or changes logs, metrics, traces, dashboards, alerts, or instrumentation.
  • type/performance

    Improves latency, throughput, memory, cost, or other performance characteristics.
  • type/refactor

    Restructures code without intentionally changing behavior.
  • type/rfc

    Design proposal or architectural direction without production implementation.
  • type/test

    Adds or improves tests without materially changing production behavior.