Label Guides

Most of the labels currently in use are the default GitHub labels, with only two additions.

first-timers - colour code (#fbca04)
feature - colour code (#0e8a16)

The general idea behind the labels should be using the base colour as a general group for the labels.

And so:

• RED - For problems (Like bugs, or issues limiting the products performance.)
• GRAY - For inactive issues (No action needed or possible. The issue is either fixed, addressed better by other issues, or just out of product scope)
• BLUE - For enhancements (Improvement on current features. Additions to increase current speed, current output and/or performance)
• GREEN - For additions (Brand new functionality. New endpoints, pages...)
• YELLOW - For miscellaneous tasks or groups (Code DRYing, folder re-structure, type of contributors...)
• PURPLE - For feedback related issues (Requires further conversation to figure out the action steps)

Most of the text and the inspiration for this guide is from this post 👉 👇 https://robinpowered.com/blog/best-practice-system-for-organizing-and-tagging-github-issues/.