GitHub issues should follow a specific protocol.
Labels
Narrowing to a specific tool
If the issue is about a specific tool, it should have a label designating which tool and type of tool it's for. Such as <tool-type>:<tool-name>.
Where <tool-type> may be ONE of: bash, python, or html. <tool-name> is the kebab case form of the name.
If this is the first time a label has been used for a specific tool name, it is likely that <tool-type>:<that tool name> will not exist as a label and you will have to create the label before it can be used.
Example:
- •
html:day-visualizer
Narrowing down to a category of issue
- •If the issue is for an enhancement, use the
enhancementlabel - •If the issue is for a bug, use the
buglabel - •If the issue is for an investigation where it's unclear if the problem is a bug or a missing feature, use the
needs-investigationlabel.
Format
If possible, the issue should describe steps used to reproduce the behavior. If the issue is particularly visual in nature, take a screenshot and attach it.