Merge pull request #220 from michaelfitzo/adding-issue-template-speci…

…fic-to-helm

Adding issue template specific to helm

.github/ISSUE_TEMPLATE/create-a-bug-report-helm.yml

@@ -0,0 +1,74 @@
+---
+name: Bug Report
+description: Use this template for reporting bugs related to gen3-helm.
+labels: bug
+assignees: []
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to create an issue. Please read the following before posting:
+
+        - DO NOT post any Personally Identifiable Information (PII) in a GitHub Issue.  This includes IP address, hostnames, and tokens.
+        - If you have questions please ask on our [Gen3 Community Slack channel](https://app.slack.com/client/T03A08KRA/C03A08KRY)! Not yet in the channel? Request Slack access [here](https://docs.google.com/forms/d/e/1FAIpQLSczyhhOXeCK9FdVtpQpelOHYnRj1EAq1rwwnm9q6cPAe5a7ug/viewform).
+        - For bugs, specify impacted services (if known), versions, errors, and explain in detail what you are trying to do.  Please provide a minimally reproducible example.
+        - Issue or Pull Request? Create only one, not both.  If unsure, start with an issue or ask on Slack.
+
+  - type: input
+    attributes:
+      label: "Name and Version"
+      description: "Name and version of the affected chart"
+      placeholder: "gen3-helm release 494"
+    validations:
+      required: true
+
+  - type: dropdown
+    attributes:
+      label: "What architecture are you using?"
+      description: "Choose the architecture of the host where the containers are executed"
+      options:
+        - amd64
+        - arm64
+
+  - type: textarea
+    attributes:
+      label: "What steps will reproduce the bug?"
+      description: "Enter details about your bug."
+      placeholder: |
+        1. In this environment...
+        2. With this config...
+        3. Run '...'
+        4. See error...
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: "What kind of cluster are you using? (e.g. Kind, Minikube, EKS, GKE, etc.)"
+
+  - type: textarea
+    attributes:
+      label: "Are you using any custom parameters or values?"
+      description: "Add any parameter used via `--set` or as a `values.yaml` customization."
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: "What is the expected behavior?"
+      description: "If possible please provide textual output instead of screenshots."
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: "What do you see instead?"
+      description: "If possible please provide textual output instead of screenshots."
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: "Additional information"
+      description: "Tell us anything you think we should know"

.github/ISSUE_TEMPLATE/create-a-feature-request.md

@@ -0,0 +1,22 @@
+---
+name: Create a Feature Request
+about: Suggest an idea for Gen3
+title: 'Feature Request: short description of your feature request'
+labels: ''
+assignees: ''
+
+---
+
+DO NOT post any Personally Identifiable Information (PII) in a GitHub Issue.  This includes IP address and hostnames.
+
+**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.