Issue Label Style Guide
Our repository covers three areas: the patterns, the language, and the guide (library folder). 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, same with the wiki.
design sitedesign guidesdesign patternsrunnerwiki
Issues that make the product feel broken or prevent us from doing further work. High priority, especially if present in production
bughotfixblockedblockerexternally blocked
Affects user's comprehension or overall enjoyment of the product.
copyuser experiencevisual design
The environment the issue pertains to.
devproduction
Necessary, but less impactful, tasks.
cleanup
Requires further conversation to figure out the action steps. Most addition ideas start from here.
request for commentshelp wantedquestionresearchstrategyready for review
Brand new functionality or guidelines. Each label corresponds to a branch prefix in our branching model (except hotfix, which is is under problems)
corefeaturelanguageguidepatternrelease
Iterations on existing features or guidelines
enhancementoptimization
Taking action, but need other things to happen first (blockers resolved, feedback given, etc…)
in progressunder consideration
No action needed or possible. The issue is either fixed, addressed better by other issues, or is just out of scope.
invalidduplicatewon't fixon hold
Our issue label style guide is based on Robin's Style Guide for Tagging