This page shortly lists the available labels and their usage. We categorise labels into three groups: _issue-type_, _workflow_, and _component_. If possible, every issue should contain one label of each group (there may be reasons to do otherwise, but consider this as general idea.
### Issue-Type
This describes the type of issue. At the moment, we have
* feature-request: A new functionality for EvoAl. Issues of this type should conform to the corresponding template 'feature-request'. Feature requests are first discussed and possibly refined (staying in `workflow::discussion`) before they're accepted as actual request and are marked as `workflow::planned` and added to a release-milestone.
* bug-report: A bug can be reported via the template `bug-report`. If its description is complete and the error can be reproduced, we'll add the label `workflow::confirmed`.
* code-quality: Tasks to improve code quality, like the addition of tests or reworkings for code-quality improvement can be issued via using the template `code-quality`.
* documentation: TBD
### Component
This describes the main component of EvoAl that is affected by the issue. It has no greater effect but supports with collecting open issues on the same component. We mainly differentiate four components:
* generator: Everything that has to do with data generation or validation.
