diff options
author | Andy Belle-Isle <drumsetmonkey@gmail.com> | 2019-08-30 00:19:31 -0400 |
---|---|---|
committer | Andy Belle-Isle <drumsetmonkey@gmail.com> | 2019-08-30 00:19:31 -0400 |
commit | bd3fe0cac583739bc0d7c4b5c8f301bb350abca0 (patch) | |
tree | 7eeb1aabcebd6999de1c3457d0882246ec0ff4d4 /deps/sol2/.github/ISSUE_TEMPLATE.md | |
parent | 2662ac356ce14dacfbc91689fd37244facff4989 (diff) |
Renamed lib to deps so github will ignore it for language stats
Diffstat (limited to 'deps/sol2/.github/ISSUE_TEMPLATE.md')
-rw-r--r-- | deps/sol2/.github/ISSUE_TEMPLATE.md | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/deps/sol2/.github/ISSUE_TEMPLATE.md b/deps/sol2/.github/ISSUE_TEMPLATE.md new file mode 100644 index 0000000..4322ab0 --- /dev/null +++ b/deps/sol2/.github/ISSUE_TEMPLATE.md @@ -0,0 +1,14 @@ +Read these guidelines. They are relatively simple and will allow me to help you better: + +1. Produce a simple, short, compilable test case that reproduces your problem. +2. Make a descriptive title that summarises the bug as a whole. +3. Explain the bug in as much detail as you can in the body of the issue. +4. Include Compiler/IDE (Visual Studio, XCode...), Build and Deployment System, Language (C++, Objective-C++), and any special defines you have set. + +If you want to request a feature: + +1. Produce any relevant imaginary code that illustrates what you would like or desired behavior. +2. Include a description and title of what you would like. +3. Annotate and describe the behavior through comments, asserts or just a small write up. + +Thanks for helping sol grow! |