Add issue templates and automatic labeling

.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,65 @@
+name: "Zopen Bug Report"
+description: Report an issue to help improve zopen
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for reporting an issue with zopen.
+
+        This issue tracker is for reporting bugs and problems related to the meta repo, which is responsible for the zopen package manager and zopen build framework.
+
+        Please fill in as much of the form below as possible to assist us in identifying and fixing the issue efficiently.
+
+  - type: textarea
+    attributes:
+      label: Description
+      description: |
+        Please explain the problem. Please also provide the exact steps that reproduce the issue. If possible, include sample code or a command line invocation.
+
+  - type: dropdown
+    attributes:
+      label: Severity
+      description: |
+        Please select the severity of the bug:
+      options:
+        - Sev 1 - Critical
+        - Sev 2 - High
+        - Sev 3 - Medium
+        - Sev 4 - Low
+
+  - type: textarea
+    attributes:
+      label: Expected Behavior
+      description: |
+        Describe the expected behavior. What did you anticipate would happen when running the tool or command?
+
+  - type: textarea
+    attributes:
+      label: Actual Behavior
+      description: |
+        What behavior did you experience instead? If possible, provide terminal output or log files (please avoid screenshots when possible).
+  - type: input
+    attributes:
+      label: z/OS Version
+      description: |
+        Specify the z/OS version you're using, including any relevant service levels (use `uname -a` for details).
+
+  - type: input
+    attributes:
+      label: zopen package manager version
+      description: |
+        Specify the version of `zopen` you are using (if applicable). You can find the version by running `zopen --version`.
+
+
+  - type: textarea
+    attributes:
+      label: Additional Information (Optional)
+      description: |
+        Share any other relevant information, such as configurations, environment variables, or any debugging attempts you've made.
+
+  - type: input
+    attributes:
+      label: Network or Security Configuration (Optional)
+      description: |
+        If relevant, describe any network or security configurations that may affect the tool's behavior (e.g., firewalls, TLS, or proxy settings).

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Zopen Community Discussions
+    url: https://github.com/IBM/zos-open-tools/discussions
+    about: Use this discussion board for sharing ideas related to the zopen community.

.github/ISSUE_TEMPLATE/feature.yml

@@ -0,0 +1,41 @@
+name: "Zopen Feature Request"
+description: Suggest a new feature or enhancement for Zopen 
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for suggesting a new feature or enhancement for Zopen.
+
+        Please provide detailed information to help us evaluate your request. The more context and examples you provide, the easier it will be to understand and prioritize your suggestion.
+
+  - type: input
+    attributes:
+      label: Feature Title
+      description: |
+        Provide a concise title for your feature request.
+
+  - type: textarea
+    attributes:
+      label: Feature Description & Current Pain Points
+      description: |
+        Describe the feature you're proposing and explain the problem or limitation it addresses. Why is this feature important to you or others? 
+
+  - type: textarea
+    attributes:
+      label: Proposed Solution & Expected Behavior
+      description: |
+        Describe how the feature should work, including details on how it fits into the existing toolset or workflow. What would the ideal behavior look like?
+
+  - type: input
+    attributes:
+      label: Environment Details (Optional)
+      description: |
+        If relevant, specify the z/OS version or `zopen` version you're using, as well as any network or security configurations that may impact this feature.
+
+  - type: textarea
+    attributes:
+      label: Additional Information (Optional)
+      description: |
+        Share any other relevant information, such as dependencies, alternative approaches you've considered, or potential challenges.
+

.github/labeler.yml

@@ -0,0 +1,8 @@
+'Sev 1 - Critical':
+    - '(Sev 1 - Critical|critical|urgent)'
+'Sev 2 - High':
+    - '(Sev 2 - High)'
+'Sev 3 - Medium':
+    - '(Sev 3 - Medium)'
+'Sev 4 - Low':
+    - '(Sev 4 - Low)'

.github/workflows/labeler.yml

@@ -0,0 +1,19 @@
+name: "Issue Labeler"
+on:
+  issues:
+    types: [opened, edited]
+
+permissions:
+  issues: write
+  contents: read
+
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: github/issue-labeler@v3.4
+      with:
+        configuration-path: .github/labeler.yml
+        not-before: 2020-01-15T02:54:32Z
+        enable-versioned-regex: 0
+        repo-token: ${{ secrets.GITHUB_TOKEN }}