github stuff

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,22 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: "[REQUEST] I want a change"
+---
+<!-- Write **BELOW** The Headers and **ABOVE** The comments else it may not be viewable -->
+
+## Is your feature request related to a problem? Please describe. 
+
+<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
+
+## Describe the solution you'd like
+
+<!-- A clear and concise description of what you want to happen. -->
+
+## Describe alternatives you've considered
+
+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
+
+## Additional context
+
+<!-- Add any other context or screenshots about the feature request here. -->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,23 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: "[BUG] Unexpected Behavior for X"
+labels: unconfirmed
+---
+<!-- Write **BELOW** The Headers and **ABOVE** The comments else it may not be viewable -->
+
+## Describe the bug
+
+<!-- Explain the bug, e.g. "When I do X, Y happens instead of Z". **Include what behavior you expected to occur here.** -->
+
+## Round ID:
+
+<!-- Include the round ID because it can help us to go through logs and find solutions easier if we need them. -->
+
+## Steps to Reproduce:
+
+<!-- Make sure you are able to reproduce it instead of just seeing the bug once, it is fine to ask on the discord about what happened but if we are unable to reproduce the bug you have seen there is a very high chance the issue will be closed. -->
+
+## Additional context
+
+<!-- Add any other context about the problem here. This is where you would include screenshots.-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,9 @@
+<!-- Write **BELOW** The Headers and **ABOVE** The comments else it may not be viewable. -->
+
+## About The Pull Request
+
+<!-- Describe The Pull Request. Please be sure every change is documented or this can delay review and even discourage maintainers from merging your PR! -->
+
+## Why It's Good For The Game
+
+<!-- Argue for the merits of your changes and how they benefit the game, especially if they are controversial and/or far reaching. If you can't actually explain WHY what you are doing will improve the game, then it probably isn't good for the game in the first place. -->