Labels are a shared vocabulary, and every change to one changes the meaning of every
issue already carrying it. This is a repository-wide edit dressed up as a small one.
list_label returns every label ordered by issuecount, most used first. That ordering is the audit: the tail is where the dead
vocabulary lives.
list_issues filtered by that label, omitting state to include open and closed issues, shows what carries
it. A label with no issues has no cost to retire; one with two hundred is load-bearing.
get_label returns its exact name, colourand description. Names are case-sensitive in ways that are easy to get wrong, and the
description is often the only record of what the label was meant to distinguish.
label_write with method set to create, update ordelete. Renaming is update with new_name.
year is a category someone will look for. Check the age of the issues carrying it
before calling it dead.
update with new_name carries every existingissue with it, keeping the history intact. Creating a second label and applying it by
hand splits the set in two, and the older issues stop appearing in the filter people
use. Rename unless the meaning is genuinely changing.
have to be moved before it is removed, and moving them is issue-by-issue work that
belongs to whoever is triaging. Say that rather than removing the label and orphaning
the classification.
existing set before picking; a new colour that clashes with an established convention
is worse than a dull one that fits.
name gets applied inconsistently, and that is the actual cause of most label sprawl.
name — required for every operation, and it is the identifier. For a rename it isthe current name; new_name is the target.
color — six hex characters with no leading marker. Required when creating.description — optional, and the difference between a scheme people follow and onethey guess at.
method — create, update, delete. There is no bulk form; each label is its owncall and its own decision.
happens to it, and how many issues it currently carries. These changes are visible to
everyone using the repository immediately.
classification does not, and it cannot be restored by recreating the label. State the
issue count and get explicit agreement naming that label.
reference the old name stop matching. Say so when the label is one of the heavily used
ones.
to produce a list with counts and ask, not an instruction to remove anything.
repository that already has its own convention is a bigger change than it looks;
propose it as one.
deliberately, or is new. Ask which before proposing a scheme.
though they display with their original case. Read the existing one and decide whether
to update it rather than retrying.
rename. Two labels cannot be collapsed by renaming one onto the other; the issues have
to be moved first.
commenting does. Report the intended changes as a list so someone else can apply them.
statewhen checking before concluding. Closed issues carry labels too, and they are the
history.
Say what was checked and what was not, so an unchecked label is not read as a clean one:
| Label | Issues carrying it | Change | Result |
|---|---|---|---|
| bug | 214 | recoloured | ✅ applied |
| wontfix | 0 | proposed for removal | ⚠️ awaiting agreement |
| stale | not checked | none | ⚠️ usage not established |