Create GitHub Issue Forms

.github/ISSUE_TEMPLATE/1_bug_report.yml

@@ -0,0 +1,104 @@
+name: Bug Report
+description: 🐞 Report a bug
+labels:
+  - kind/bug
+body:
+  - type: textarea
+    attributes:
+      label: Which area is this bug related to?
+      description: Choose the area(s) this bug is related to.
+      value: |
+        > /area ci
+        > /area api
+        > /area library
+        > /area registry
+        > /area registry-viewer
+        > /area alizer
+        > /area devworkspace
+        > /area integration-tests
+        > /area test-automation
+        > /area releng
+        > /area landing-page
+      placeholder: |
+        > /area ci
+        > /area api
+        > /area library
+        > /area registry
+        > /area registry-viewer
+        > /area alizer
+        > /area devworkspace
+        > /area integration-tests
+        > /area test-automation
+        > /area releng
+        > /area landing-page
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: What versions of software are you using?
+      description: Choose and fill in the applicable sections.
+      value: |
+            #### Go Project
+
+            **Operating System and version:**
+
+            **Go Pkg Version:**
+
+            #### Node.js Project
+
+            **Operating System and version:**
+
+            **Node.js version:**
+
+            **Yarn version:**
+
+            **Project.json:**
+
+            #### Web Browser
+
+            **Operating System and version:**
+
+            **Browser name and version:**
+  - type: textarea
+    attributes:
+      label: Bug Summary
+      description: A clear and concise description of what the bug is and steps to reproduce the behavior.
+      value: |
+        **Describe the bug:**
+
+        **To Reproduce:**
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Expected Behavior
+      description: A clear and concise description of what you expected to happen.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable
+      description: |
+        To get logs:
+            ci: please copy the github workflow output
+            api: please copy the terminal output
+            library: please copy the terminal output
+            registry: follow instruction under "Collecting Logs" to find log: https://github.com/devfile/registry-support/blob/main/TROUBLESHOOTING.md
+            devworkspace: copy the logs from the controller (kubectl logs deploy/devworkspace-controller -n $NAMESPACE)
+            test-automation:
+                api: follow instruction under "Running tests locally" to find test log: https://github.com/devfile/api/tree/main/test
+                library: follow instruction under "Running the tests locally" to find test log: https://github.com/devfile/library/tree/main/tests
+                devworkspace: copy the logs from the controller (kubectl logs deploy/devworkspace-controller -n $NAMESPACE)
+            integration-tests: please copy the build log under prow ci result for QE ingetration tests
+  - type: textarea
+    attributes:
+      label: Additional Context
+      description: Add any other context about the problem here.
+  - type: textarea
+    attributes:
+      label: Any workaround?
+      description: Describe the workaround if applicable.
+  - type: textarea
+    attributes:
+      label: Suggestion on how to fix the bug
+      description: Provide suggestion on how to fix the bug upon your investigation, if applicable.

.github/ISSUE_TEMPLATE/2_user_story.yml

@@ -0,0 +1,52 @@
+name: User Story
+description: 📝 User story for new enhancement
+labels:
+  - kind/user-story
+body:
+  - type: textarea
+    attributes:
+      label: Which area is this user story related to?
+      description: Choose the area(s) this story is related to.
+      value: |
+        > /area ci
+        > /area api
+        > /area library
+        > /area registry
+        > /area registry-viewer
+        > /area alizer
+        > /area devworkspace
+        > /area integration-tests
+        > /area test-automation
+        > /area releng
+        > /area landing-page
+      placeholder: |
+        > /area ci
+        > /area api
+        > /area library
+        > /area registry
+        > /area registry-viewer
+        > /area alizer
+        > /area devworkspace
+        > /area integration-tests
+        > /area test-automation
+        > /area releng
+        > /area landing-page
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: User Story
+      description: Describe the user, action, and intention of the story then a clear and concise description of what needs to be done to achieve this story.
+      placeholder: As a ... I want to ..., so that ...
+      value: As a ... I want to ..., so that ...
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Acceptance Criteria
+      description: Decide which specific steps need to be completed, outline subtasks.
+      value: |
+        - [ ] ....
+        - [ ] ....
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/3_task.yml

@@ -0,0 +1,53 @@
+name: Task
+description: 🔧 Issue for project support and quality assurance
+labels:
+  - kind/task
+body:
+  - type: textarea
+    attributes:
+      label: Which area is this issue related to?
+      description: Choose the area(s) this task is related to.
+      value: |
+        > /area ci
+        > /area api
+        > /area library
+        > /area registry
+        > /area registry-viewer
+        > /area alizer
+        > /area devworkspace
+        > /area integration-tests
+        > /area test-automation
+        > /area releng
+        > /area landing-page
+      placeholder: |
+        > /area ci
+        > /area api
+        > /area library
+        > /area registry
+        > /area registry-viewer
+        > /area alizer
+        > /area devworkspace
+        > /area integration-tests
+        > /area test-automation
+        > /area releng
+        > /area landing-page
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Issue Description
+      description: A clear and concise description of what the task is.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Acceptance Criteria
+      description: Decide which specific steps need to be completed, outline subtasks.
+      value: |
+        - [ ] ....
+        - [ ] ....
+  - type: input
+    attributes:
+      label: Target Odo Version
+      description: Provide the target Odo version if this task is for QE integration test.
+      value: 'Target Odo version: <odo-version>'

.github/ISSUE_TEMPLATE/4_feature_request.yml

@@ -0,0 +1,61 @@
+name: Feature Request
+description: 💡 Suggest an idea for this project
+labels:
+  - kind/enhancement 
+body:
+  - type: textarea
+    attributes:
+      label: Which area is this feature related to?
+      description: Choose the area(s) this feature is related to.
+      value: |
+        > /area ci
+        > /area api
+        > /area library
+        > /area registry
+        > /area registry-viewer
+        > /area alizer
+        > /area devworkspace
+        > /area integration-tests
+        > /area test-automation
+        > /area releng
+        > /area landing-page
+      placeholder: |
+        > /area ci
+        > /area api
+        > /area library
+        > /area registry
+        > /area registry-viewer
+        > /area alizer
+        > /area devworkspace
+        > /area integration-tests
+        > /area test-automation
+        > /area releng
+        > /area landing-page
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Which functionality do you think we should add?
+      description: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+      value: |
+        **Why is this needed? Is your feature request related to a problem?**
+
+        **Detailed description:**
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe the solution you'd like
+      description: A clear and concise description of what you want to happen.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe alternatives you've considered
+      description: A clear and concise description of any alternative solutions or features you've considered.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Additional Context
+      description: Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/5_documentation.yml

@@ -0,0 +1,43 @@
+name: Documentation
+description: 📖 Suggest an update for devfile documentation
+labels:
+  - area/documentation
+body:
+  - type: textarea
+    attributes:
+      label: Which area is this documentation change related to?
+      description: Choose the area(s) this documentation change refer to.
+      value: |
+        > /area ci
+        > /area api
+        > /area library
+        > /area registry
+        > /area registry-viewer
+        > /area alizer
+        > /area devworkspace
+        > /area integration-tests
+        > /area test-automation
+        > /area releng
+        > /area landing-page
+      placeholder: |
+        > /area ci
+        > /area api
+        > /area library
+        > /area registry
+        > /area registry-viewer
+        > /area alizer
+        > /area devworkspace
+        > /area integration-tests
+        > /area test-automation
+        > /area releng
+        > /area landing-page
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Issue Details
+      description: Provide a clear and concise description of the changes you are suggesting
+      value: |
+        **What mistake did you find / what is missing in the documentation?**
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/6_registry_update.yml

@@ -0,0 +1,33 @@
+name: Emergency Registry Update
+description: ⚠️ Request for an emergency registry update
+title: "[Maintenance]: Promote stack <name> changes to production"
+labels:
+  - area/registry
+body:
+  - type: input
+    attributes:
+      label: Task Assignee
+      description: |
+        The assignee for the task of updating the stack in question. Usually should be devfile/devfile-registry-maintainers
+        unless otherwise specified.
+      placeholder: '@devfile/devfile-registry-maintainers'
+      value: '@devfile/devfile-registry-maintainers'
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Request Details
+      description: |
+        The staging devfile registry, https://registry.stage.devfile.io is refreshed upon each commit to main in this repository.
+        Production, https://registry.devfile.io, is promoted manually each Wednesday, as needed.
+
+        If you are a stack or sample owner and need to request an urgent refresh of https://registry.devfile.io before Wednesday (for example if a stack is broken),
+        please fill out the issue template below.
+      value: |
+        **Stack name:**
+
+        **Why is the refresh needed:**
+
+        **Why the refresh cannot wait until the next regularly scheduled refresh:**
+    validations:
+      required: true