Skip to main content
Labels are lightweight metadata tags you attach to issues, pull requests, and discussions to categorize, prioritize, and triage work. When applied consistently, labels help teams filter work, create custom views, and speed up contributor onboarding by making the intent and context of an item immediately visible.
The image shows a task management system interface with open and closed issues, each labeled with descriptions like "good first issue" and "help wanted." The interface includes filters for "Open" and "Closed" issues, author details, and milestones.
Labels are repository-scoped and reusable across that repository. They typically describe the nature, priority, or status of a work item. Below are common standard labels and when to use them. In addition to these defaults, create custom labels to match your workflow (e.g., needs-triage, high priority, security). Use a consistent naming and color scheme so contributors can interpret label meanings reliably across the repository.
Labels are scoped to individual repositories. Define a documented naming standard and color palette so contributors and automation can consistently interpret label intent.

​
Searching and automating with labels

Labels enable powerful filtering and can trigger automation such as GitHub Actions or project workflows. Example: find open issues labeled as high priority:
Example GitHub Actions trigger that responds when an issue is labeled:
Within such a workflow you can inspect the label name and automate tasks like assigning reviewers, adding additional labels, posting comments, or moving items between project columns.
Avoid label sprawl. Too many overlapping labels reduce clarity—periodically audit labels, merge similar ones, and document meaning to keep the system useful.

​
Best practices

  • Document your label taxonomy in CONTRIBUTING.md or a repository README so newcomers can find and use labels correctly.
  • Limit the number of “status” labels (e.g., triaged, in progress, blocked) vs. semantic labels (e.g., bug, enhancement) to avoid confusion.
  • Standardize colors and prefixes if you use cross-repo conventions (e.g., priority:high, area:frontend).
  • Automate routine label actions where possible (assign owners, set SLA reminders, move project cards).
  • Use good first issue and help wanted to increase discoverability—GitHub indexes these labels for external contributors.
By defining clear labels and keeping them organized, your project will gain faster triage, better routing of work, and an improved contributor experience.

Watch Video