@@ -4,7 +4,7 @@ This page shortly lists the available labels and their usage. We categorise labe
This describes the type of issue. At the moment, we have
* ~"issue-type::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.
* ~"issue-type::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.
* ~"issue-type::bug" 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".
* ~"issue-type::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`.
* ~"issue-type::documentation" Requests for extending or improving the documentation in the Wiki (or the DSLs).
