* optimisation: Everything relating to optimisation algorithms.
*languages: Additions to languages, semantic checks, added parameters or options - this is your component.
*core: Everything concerning the main functionality of EvoAl.
### Workflow
TBD
\ No newline at end of file
Workflow labels describe the current status of the issue in shorthand.
* discussion: Issues marked as discussion are not yet well-defined or confirmed, and can therefore not be mapped to a milestone.
* confirmed: At the moment, this is usually only used for bugs, and is added as soon as there is enough information present to reproduce and thus confirm the bug.
* planned: When an issue is well-defined, it can be moved to a release and is thus marked planned.
* doing: To be named `doing`, an issue has to be well-defined, planned and assigned to an assignee.
* testing: If applicable (e.g. for feature requests or bugs), issues are tested after they have exited the doing phase.
* done: Assignee views this as done, needs four-eye principle to be closed.
