Adding issue and pr templates to Github

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,68 @@
+name: Bug Report
+description: File a bug report.
+title: "[Bug]: "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report! Please, fill this form to help us improve the project.
+  - type: checkboxes
+    attributes:
+      label: Is there an existing issue for this?
+      description: Please search to see if an issue already exists for the bug you encountered.
+      options:
+        - label: I have searched the existing issues
+          required: true
+  - type: dropdown
+    id: version
+    attributes:
+      label: Version
+      description: What was the version this was found on?
+      multiple: true
+      options:
+        - ISPN 15
+        - ISPN 14
+        - Downstream version
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Current Behavior
+      description: A concise description of what you're experiencing.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Expected Behavior
+      description: A concise description of what you expected to happen.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Steps To Reproduce
+      description: Steps to reproduce the behavior.
+      placeholder: |
+        1. In this environment...
+        2. With this config...
+        3. Run '...'
+        4. See error...
+  - type: dropdown
+    id: browsers
+    attributes:
+      label: What browsers are you seeing the problem on?
+      multiple: true
+      options:
+        - Firefox
+        - Chrome
+        - Safari
+        - Microsoft Edge
+    validations:
+      required: false
+  - type: textarea
+    id: anything-else
+    attributes:
+      label: Anything else
+      description: Any additional information you'd like to share
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/feature_request.yaml

@@ -0,0 +1,25 @@
+name: Feature request
+description: Suggest an idea for this project.
+title: "[Feature Request]: "
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this feature request! Please, fill this form to help us improve the project.
+  - type: textarea
+    id: description
+    attributes:
+      label: Feature description
+      description: A clear and concise description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Anything else?
+      description: |
+        Links? References? Add any other context or screenshots about the feature request here.
+
+        Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in.
+    validations:
+      required: false

.github/pull_request_template.md

@@ -0,0 +1,27 @@
+<!--- If this is a non-code change, this template is not required; reference any issues or top-level descriptions as needed -->
+<!--- All code change PRs should relate to an issue, reference it here; see example below -->
+<!--- Closes: #123 -->
+
+## Description
+<!--- Describe your changes in detail; the what, the why, any findings, etc -->
+<!--- Include any screenshots of changed UI; Include any gifs if it was a flow / UX change -->
+
+## How Has This Been Tested?
+<!--- Please mention to steps to reproduce to see changes. -->
+<!--- Include details of your testing environment, and the tests you ran to -->
+<!--- see how your change affects other areas of the code, etc. -->
+
+## Test Impact
+<!--- What tests have you done to covert implemented functionality -->
+<!--- If tests are not applicable, explain why here -->
+
+## Request review criteria:
+<!--- This PR will be merged by any repository approver when it meets all the points in the checklist -->
+<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+
+Self checklist (all need to be checked):
+- [ ] The developer has manually tested the changes and verified that the changes work
+- [ ] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
+- [ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
+- [ ] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)
+- [ ] Included any necessary screenshots or gifs if it was a UI change.