Added issue templates (piotrwitek#192)

Author: piotrwitek

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,34 @@
+---
+name: Bug report
+about: Create a report to help us improve
+---
+
+## Description
+<!-- A clear description of what the bug is -->
+
+## Steps to Reproduce
+<!--
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+-->
+
+## Expected behavior
+<!-- A clear description of what you expected to happen -->
+
+## Suggested solution(s)
+<!-- How could we solve this bug. What changes would need to be made -->
+
+## Project Dependencies
+- TypeScript Version: X.X.X
+- tsconfig.json:
+<!-- Paste contents of your tsconfig.json here -->
+
+## Environment (optional)
+<!-- Fill if you think it's relevant to your issue -->
+- Browser and Version: XXX
+- OS: XXX
+- Node Version: XXX
+- Package Manager and Version: XXX

.github/ISSUE_TEMPLATE/custom.md

@@ -0,0 +1,9 @@
+---
+name: Question
+about: Have a question? Please check our spectrum community chat.
+---
+
+First of all please check our spectrum community chat and we recommend to ask your question there for a quickest response and the indexing in search engines: 
+- https://spectrum.chat/react-redux-ts
+
+The only good reason to use issue tracker for your questions would be for "special requests" that doesn't fit into bug reports and feature requests categories.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,19 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+---
+
+## Is your feature request related to a real problem or use-case?
+<!-- A clear description of your problem or use-case-->
+
+## Describe a solution including usage in code example
+<!-- A clear description of the solution including usage with complete code examples, nicely formatted with "```ts" tags (especially if that's a new api proposal) -->
+
+## Who does this impact? Who is this for?
+<!-- Who is this for? All users? TypeScript users? Yourself? People using X, Y, Z, etc.? -->
+
+## Describe alternatives you've considered (optional)
+<!-- A clear and concise description of any alternative solutions or workaround you've considered  -->
+
+## Additional context (optional)
+<!-- Add any other stuff you need, like links or related issues -->