-
Notifications
You must be signed in to change notification settings - Fork 121
chore: create new label taxonomy and remove old labels #691
Description
Part of #690
Create the 40 labels defined in the umbrella issue and delete the 27 old labels they replace. This should be done in a single pass to avoid confusion.
Steps
- Create all
kind/*,area/*,priority/*,status/*,pr/*,lifecycle/*labels with correct colors - Rename
release-issues→release,gsoc2026→gsoc - Delete old labels after migration is complete (sub-issues 2 and 3)
Labels to create (40)
kind/: kind/bug, kind/feature, kind/improvement, kind/documentation, kind/cleanup, kind/question, kind/umbrella
area/: area/core, area/ui, area/storage, area/streaming, area/hooks, area/tracking, area/integrations, area/visualization, area/website, area/ci, area/examples, area/typing
priority/: priority/critical, priority/high, priority/medium, priority/low
status/: status/needs-triage, status/needs-info, status/accepted, status/blocked, status/wontfix
pr/: pr/do-not-merge, pr/ready-to-merge, pr/needs-rebase, pr/stale
lifecycle/: lifecycle/stale, lifecycle/frozen
special: breaking-change, gsoc (rename), release (rename), hacktoberfest (keep)
Labels to delete (27)
invalid, duplicate, launch, exploratory, product direction, design decision, hamilton, AWS, gsoc2026, javascript, release-issues, exceptions, triage, bug, documentation, enhancement, question, wontfix, repo hygiene, parallelism, visibility, ui, storage, integrations, visualization, hooks, examples, umbrella
Note: Labels must be migrated on existing issues/PRs before deletion (see #690 sub-issues 2 and 3).