Issue Label Style Guide

Our issue label style guide is based on Robin's Style Guide for Tagging

Platform

Our repository covers three areas: the patterns, the language, and the library. Issues will be related to one of those three areas. If an issue is related to the task runner, it should get labeled as such

Color: #C0E6FF

• design language
• design library
• design patterns
• runner

Problems

Issues that make the product feel broken or prevent us from doing further work. High priority, especially if present in production

Color: #FF5050

• bug
• hotfix
• blocked
• externally blocked

Mindless

Necessary, but less impactful, tasks.

Color: #FFD791

• cleanup

Experience

Affects user's comprehension or overall enjoyment of the product.

Color: #FFA573

• copy
• user experience
• visual design

Environment

The environment the issue pertains to.

Color: #E9E0E0

• dev
• production

Feedback

Requires further conversation to figure out the action steps. Most addition ideas start from here.

Color: #DB2780

• request for comments
• help wanted
• question
• research
• strategy
• ready for review

Improvement

Iterations on existing features or guidelines

Color: #41D6C3

• enhancement
• optimization

Additions

Brand new functionality or guidelines. Each label corresponds to a branch prefix in our branching model (except hotfix, which is is under problems)

Color: #8CD211

• core
• feature
• language
• library
• pattern
• release

Pending

Taking action, but need other things to happen first (blockers resolved, feedback given, etc…)

Color: #FDD600

• in progress
• under consideration

Inactive

No action needed or possible. The issue is either fixed, addressed better by other issues, or is just out of scope.

Color: #DFE9E9

• invalid
• duplicate
• won't fix