Lables
Labeled for priority/type (e.g. bug, enhancement).
Labels help categorize and prioritize work. Use these standardized labels:
Compatibility
Label | Description | Color |
---|---|---|
Compat/Breaking | Breaking change (requires major version bump) |
Type (Kind)
Label | Description | Color |
---|---|---|
Kind/Bug | Something isn't working | |
Kind/Documentation | Docs improvements | |
Kind/Enhancement | Improve existing functionality | |
Kind/Feature | New functionality | |
Kind/Security | Security vulnerability/fix | |
Kind/Testing | Test-related changes |
Priority
Label | Description | Color |
---|---|---|
Priority::Critical | System-breaking issue | |
Priority::High | Major impact on usability | |
Priority::Medium | Moderate impact | |
Priority::Low | Minor/cosmetic improvement |
Review Status
On GitLab use status instead.
Label | Description | Color |
---|---|---|
Reviewed::Confirmed | Issue verified by maintainers | |
Reviewed::Duplicate | Already exists | |
Reviewed::Invalid | Not a valid issue | |
Reviewed::Won't Fix | Intentionally not addressed |
Workflow Status
On GitLab use status instead.
Label | Description | Color |
---|---|---|
Status::Abandoned | Work started but abandoned | |
Status::Blocked | Blocked by external factors | |
Status::Need More Info | Requires user feedback |
Test Status
Label | Description | Color |
---|---|---|
Test::Manual | Manual testing has been documented | |
Test::Needed | Test should be added | |
Test::Needs Help | Help needed to add a test | |
Test::Not Needed | No additional test is needed | |
Test::Present | Test has been added |
Project
On GitLab use status instead.
Label | Description | Color |
---|---|---|
Project::Backlog | Items waiting to be prioritized for future development | |
Project::Todo | Tasks ready to be worked on in the current sprint | |
Project::In Progress | Work items currently being developed by team members | |
Project::Done | Completed tasks ready for deployment or review |
Automation
Label | Description | Color |
---|---|---|
Bot/Automated Fix | Applied to MRs created automatically by the CI pipeline to fix linting, formatting, or other code quality issues | |
Bot/Dependency Update | Applied to MRs created automatically by a dependency bot (like RenovateBot or Dependabot) to update dependencies | |
CI/Build Failure | Applied to issues that are tracking a recurring or hard-to-fix build failure in the CI/CD pipeline | |
CI/Skip | Can be manually applied to an MR to signal that its CI pipeline should be skipped (requires manual intervention or a specific CI rule) |
Operating System
Label | Description | Color |
---|---|---|
OS/Windows | Windows operating system | |
OS/macOS | macOS operating system | |
OS/Linux | Linux operating system | |
OS/FreeBSD | FreeBSD operating system | |
OS/OpenBSD | OpenBSD operating system | |
OS/BSD | Generic BSD operating system |
Architecture
Label | Description | Color |
---|---|---|
Arch/amd64 | x86-64 architecture | |
Arch/arm64 | ARM 64-bit architecture |
Status (GitLab)
Label | Type | Description | Color |
---|---|---|---|
Backlog (Open default) | Triage | Items waiting to be prioritized for future development | |
To do | To do | Tasks ready to be worked on in the current sprint | |
In progress | In progress | Work items currently being developed by team members | |
Done (Closed default) | Done (Closed) | Completed tasks ready for deployment or review | |
Won't do | Canceled (Closed) | Intentionally not addressed | |
Duplicate (Duplicate default) | Canceled (Closed) | Already exists | |
Invalid | Canceled (Closed) | Not valid | |
Abandoned | Canceled (Closed) | Work started but abandoned | |
Need More Info | Canceled (Closed) | Requires user feedback | |
Blocked | Canceled (Closed) | Blocked by external factors |
Last updated on