feat(template): add issue and pull request template

Author: theEvilReaper

.github/ISSUE_TEMPLATE/behavior-bug.yml

@@ -0,0 +1,24 @@
+name: "Bug Report"
+description: "Report a bug"
+title: "[Bug] "
+labels:
+  - bug
+body:
+  - type: textarea
+    attributes:
+      label: "Describe the bug"
+      description: |
+        A clear and concise description of what the bug is.
+        If you have a screenshot of the bug, please attach it below.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: "Steps to reproduce the bug"
+      description: "Tell us exactly how to reproduce the bug you are experiencing."
+      placeholder: |
+        1. ...
+        2. ...
+        3. ...
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: GitHub Discussions
+    url: https://github.com/theEvilReaper/Bounce/discussions
+    about: If you have any questions or concerns (if you dont want to use Discord), please post them in our GitHub Discussions.

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -0,0 +1,23 @@
+name: "Feature request"
+description: "Suggest a new feature or enhancement"
+title: "Feature: "
+labels: [ "feature" ]
+body:
+  - type: textarea
+    attributes:
+      label: Describe the feature
+      description: |
+        A clear and concise description of what the feature is.
+        If you have a screenshot of the feature, please attach it below.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Why is this feature important to you?
+      description: Tell us why you think this feature is important to you
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Additional context
+      description: Add any other context or screenshots about the feature request here

.github/pull_request_template.md

@@ -0,0 +1,29 @@
+## Proposed changes
+
+Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
+If it fixes a bug or resolves a feature request, be sure to link to that issue.
+
+## Types of changes
+
+What types of changes does your code introduce to this project?
+_Put an `x` in the boxes that apply_
+
+- [ ] Bugfix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation Update (if none of the other choices apply)
+
+## Checklist
+
+_Put an `x` in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
+them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
+merging your code._
+
+- [ ] I have read the CONTRIBUTING.md
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] I have added necessary documentation (if appropriate)
+
+## Further comments
+
+If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you
+did and what alternatives you considered, etc...