Updated issues template

.github/ISSUE_TEMPLATE.md

@@ -1,9 +0,0 @@
-This repo is for Phaser 3 related issues only. If you've found an issue with Phaser 2 please see the [Phaser CE (Community Edition)](https://github.com/photonstorm/phaser-ce) repo instead.
-
-This should not be used for technical support. If you're struggling trying to use Phaser then post your question to the [forum](http://www.html5gamedevs.com/forum/33-phaser-3/), [Slack](https://phaser.io/community/slack) or [Discord](https://phaser.io/community/discord) channels. GitHub Issues are for bugs and feature requests only.
-
-API errors must include example code showing what happens, and why you don't believe this is the expected behavior. Issues posted without code take _far_ longer to get resolved, _if ever_. Feel free to use a site such as jsBin or [CodePen](https://codepen.io/pen?template=YeEWom) to demo the problem. If we can run it, and see the error, we can usually fix it.
-
-If your Issue contains _any_ form of hostility it will be instantly closed and you will be blocked from access to all our repos.
-
-**Be nice. We do this for free.**

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,59 @@
+---
+name: "\U0001F41B Bug Report"
+about: Report a bug found while using Phaser 3
+
+---
+
+<!--
+Thank you for taking the time to contribute towards Phaser. Before submitting your issue, check the following:
+
+1. This repo is for Phaser 3 only. Phaser 2.x issues should be raised in the [Phaser CE](https://github.com/photonstorm/phaser-ce) repo.
+
+2. This repo should not be used for technical support. If you're struggling to use Phaser then post your question to the [forum](http://www.html5gamedevs.com/forum/33-phaser-3/), [Slack](https://phaser.io/community/slack) or [Discord](https://phaser.io/community/discord) channels. GitHub Issues are for bugs and feature requests only.
+
+3. Make sure your issue isn't a duplicate, or has already been fixed.
+
+4. If your issue contains _any_ form of hostility it will be closed and you will be blocked from access to all our repos. Be nice. We do this for free.
+
+5. If all the above is ok, fill out the template below.
+-->
+
+
+## Version
+<!--
+Enter the version of Phaser you're using. You can find this output to the Dev Tools console in your browser.
+-->
+* Phaser Version:
+<!--
+Place the operating system **below** this comment.
+-->
+* Operating system:
+<!--
+If the bug is browser specific, please enter the version **below** this comment:
+-->
+* Browser:
+
+
+## Description
+
+<!--
+Write a detailed description of the bug **below** this comment. Include the expected behavior and what actually happens. If the issue is device specific, please say so.
+-->
+
+
+## Example Test Code
+
+<!--
+All issues must have source code demonstrating the problem. We automatically close issues after 30 days if no code is provided.
+
+The code can be pasted directly below this comment, or you can link to codepen, jsbin, or similar. The code will ideally be runnable instantly. The more work involved in turning your code into a reproducible test case, the longer it will take the fix the issue.
+-->
+
+
+## Additional Information
+
+<!--
+Is there anything else you think would be useful for us to reproduce the error? Do you have a solution in mind?
+
+If you have any screen shots or gifs demonstrating the issue (if it can't be seen when running your code), please include those too.
+-->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,15 @@
+---
+name: "\U0001F389 Feature Request"
+about: Share an idea about a feature you'd like to see in Phaser
+
+---
+
+**We're constantly trying to make Phaser 3 better**
+
+So we'd love to hear about feature requests for the v3 API. Screenshots, example code or links to blog posts / other APIs are encouraged.
+
+Please try and keep the requests sensible. We will only keep those we feel are within our abilities to add to Phaser, or that are a good fit for our API.
+
+**[Optional] Do you want to help provide this feature?**
+
+If you would like to get involved in helping build the feature, please let us know. We can then discuss implementation with you and the best way to approach it. Again, screenshots or mockups are really useful.

.github/no-response.yml

@@ -0,0 +1,14 @@
+# Configuration for no-response - https://github.com/probot/no-response
+
+# Number of days of inactivity before an Issue is closed for lack of response
+daysUntilClose: 30
+# Label requiring a response
+# TODO: also close `needs-reproduction` issues (blocked by https://github.com/probot/no-response/issues/11)
+responseRequiredLabel: 🤷‍♂️ More info needed
+# Comment to post when closing an issue due to lack of response. 
+closeComment: >
+Thank you for taking time to open this issue.
+
+We haven’t gotten a response to our questions above. With the details currently given in the issue we don’t have enough information to take action.
+
+So we’re going to close this issue. We can re-open it if you find the time to provide the information we need.