Manage Repository Labels in GitHub
Use a maintained repository label set to classify work and make triage predictable. Labels belong to repositories; editing a label in one repository does not automatically update others.
Step-by-step guide
Check access and scope
Creating labels requires repository write access. Agree on meanings before changing labels used by filters, release notes or workflows.
Audit labels and consumers
Review existing labels and their consumers.
Define taxonomy dimensions
Choose clear dimensions such as area, priority or evidence need.
- Worked example: Use area:identity for invitation-token work and needs:reproduction for missing evidence. Keep the dimensions separate so a triage filter does not depend on combined labels with unclear meaning.
Create described labels
Create or edit labels with short descriptions.
Classify representative work
Apply the taxonomy to representative issues and pull requests.
Review missing labels
Review unlabeled items and obsolete synonyms.
Verify the result
A maintainer can explain each label and the important saved searches still return expected work.
Common mistakes
Check the handoff edge case
Combining area, priority and evidence state in one label multiplies categories. Keep independent dimensions separate.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.