test

[stephanbcbauer]

WHAT

// describes the desired functionality and how the feature should behave. This should include clear requirements, and a "definition-of-done", i.e. what the result of the issue should be. This is important for concept, documentation or ideation issues

WHY

// outlines the motivation, why the feature is desired, and possibly what the impact is if the feature is not
implemented. "Because we need it" is not a sufficient reason!

HOW

// if possible, outlines a solution proposal

FURTHER NOTES

// anything else you want to outline

Please be sure to take a look at
our contribution guidelines and
our PR etiquette.

[stephanbcbauer]

was just a test