From aa4b1ea0de536def45003e81f58418a8a57a6e1f Mon Sep 17 00:00:00 2001 From: Dmitriy Zhavoronkov Date: Mon, 17 Aug 2026 19:49:49 +0200 Subject: [PATCH] docs: expand label vocabulary with type/domain/priority namespaces MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The triage-labels reference previously covered only the five triage roles. The repo has since adopted a namespaced label taxonomy: - type: required, one of feature / bug / refactor / docs / chore - domain: optional, 0–2 of provider / ui / settings / security / service / infra - triage: issues only (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) - priority: optional (critical / high / low) Restructure the doc into these four sections so agents and contributors work from one source of truth. Redundant labels (invalid, duplicate, question, good first issue, help wanted, P0) were dropped in the same sweep; the old bare labels (bug, enhancement, documentation, provider, ui, settings, security, service) were renamed into the new namespaces, preserving all existing label associations. --- docs/agents/triage-labels.md | 39 ++++++++++++++++++++++++++++++++++-- 1 file changed, 37 insertions(+), 2 deletions(-) diff --git a/docs/agents/triage-labels.md b/docs/agents/triage-labels.md index f1c58aa..66860c5 100644 --- a/docs/agents/triage-labels.md +++ b/docs/agents/triage-labels.md @@ -1,4 +1,10 @@ -# Triage label vocabulary +# Label vocabulary + +All labels are namespaced. Every PR gets exactly one `type:` label and 0–2 +`domain:` labels. Issues additionally get one triage label and, when relevant, +one `priority:` label. + +## Triage (issues) Use these exact labels when triaging incoming issues: @@ -10,4 +16,33 @@ Use these exact labels when triaging incoming issues: | Ready for human | `ready-for-human` | Requires human implementation or intervention. | | Will not fix | `wontfix` | Will not be actioned. | -Do not invent alternate labels unless this mapping is deliberately updated. \ No newline at end of file +## Priority (optional, issues) + +| Label | Meaning | +| --- | --- | +| `priority: critical` | Blocks release or breaks production. | +| `priority: high` | Impacts users; should ship soon. | +| `priority: low` | Nice-to-have; can be deferred. | + +## Type (required on every PR and issue) + +| Label | Meaning | +| --- | --- | +| `type: feature` | New feature or enhancement. | +| `type: bug` | Defect or unexpected behavior. | +| `type: refactor` | Code quality change with no behavior change. | +| `type: docs` | Documentation only. | +| `type: chore` | CI, build, deps, config. | + +## Domain (optional, may combine) + +| Label | Scope | +| --- | --- | +| `domain: provider` | AI provider integrations. | +| `domain: ui` | UI/UX (status bar, dialogs, tooltips). | +| `domain: settings` | Plugin configuration. | +| `domain: security` | Credentials, PasswordSafe, OAuth. | +| `domain: service` | Background services, refresh, caching. | +| `domain: infra` | CI/CD, build, gradle. | + +Do not invent alternate labels unless this mapping is deliberately updated.