fluidsynth/.github/issue_template.md
Tom M e4140e8a77
Update issue_template.md
put emphasis on using this template
2018-02-22 20:21:24 +01:00

40 lines
1.5 KiB
Markdown

<!--
Before submitting an issue, consider looking into our
wiki ( https://github.com/FluidSynth/fluidsynth/wiki ) or the
developer resources ( http://www.fluidsynth.org/api/ )
Please do not submit support requests or "How to" questions here. Instead, use FluidSynth's
mailing list: https://lists.nongnu.org/mailman/listinfo/fluid-dev
Below is a form that shall help getting relevant information for bugs and feature requests together.
We strongly recommend to use it! Feel free to edit or remove inapplicable/unneeded parts.
-->
### FluidSynth version <!-- enter FluidSynths version you're using -->
1.1.x
### Current behavior
<!-- Describe the current situation, e.g. how the bug manifests. -->
### Expected behavior
<!-- Describe what the behavior would be without the bug or how the
feature request would make your life easier. -->
### Steps to reproduce
<!-- Please explain the steps required to duplicate the issue,
esp. if you are able to provide a sample application.
E.g. how to start fluidsynth, what shell commands to enter, what midi events to send, etc. -->
### Other information
<!-- If you are able to illustrate the bug or feature request with an example, please provide simple
source code below or as attatched file. List any other information that is relevant to your issue:
Stack traces,
related issues,
build logs,
suggestions on how to fix,
links to related discussions at fluid-dev
etc.
-->
```
insert code snippets, soundfonts or anything relevant here, or attach it as extra file(s) if it's too much
```