chore: Updated issue and pr template

.github/ISSUE_TEMPLATE/bug.yaml

@@ -2,6 +2,7 @@ name: "🐛 Bug Report"
 description: "Submit a bug report to help us improve"
 title: "Bug: "
 labels: [bug]
+assignees: ["prakarsh-dt","anupdhiran"]
 body:
   - type: markdown
     attributes:
@@ -39,25 +40,22 @@ body:
       label: "👎 Actual Behavior"
       description: "What did actually happen? Add screenshots, if applicable."
       placeholder: "It actually ..."
-  - type: dropdown
-    id: device
+  - type: textarea
+    id: kuberentes-version
     attributes:
-      label: "💻 Device"
-      description: "Which device running on?"
-      options:
-        - Desktop/Laptop
+      label: "☸ Kubernetes version"
+      description: "What is your Kubernetes service and version?"
+      placeholder: "EKS 1.23, KOps 1.22, AKS 1.21 etc."
     validations:
       required: true
-  - type: dropdown
-    id: operating-system
+  - type: textarea
+    id: cloudProvider
     attributes:
-      label: "💻 Operating system"
-      description: "What OS is your app running on?"
-      options:
-        - Linux
-        - MacOS
-        - Windows
-        - Something else
+      label: "Cloud provider"
+      value: |
+        <details>
+
+        </details>
     validations:
       required: true
   - type: dropdown

.github/ISSUE_TEMPLATE/documentation.yaml

@@ -1,5 +1,6 @@
 name: "📚 Documentation"
 description: "Report an issue related to documentation"
+assignees: ["SNe789","prakarsh_dt"]
 title: "Doc: "
 labels: [documentation]
 body:

.github/ISSUE_TEMPLATE/feature.yaml

@@ -2,6 +2,7 @@ name: 🚀 Feature
 description: "Submit a proposal for a new feature"
 title: "Feature: "
 labels: [feature]
+assignees: ["prakarsh_dt","nishant-d","anupdhiran"]
 body:
   - type: markdown
     attributes:
@@ -34,7 +35,7 @@ body:
   - type: textarea
     id: alternative
     validations:
-      required: true
+      required: false
     attributes:
       label: "🔄️ Alternative"
       description: "A clear and concise description of any alternative solutions or features you've considered."

.github/pull_request_template.md

@@ -1,32 +1,49 @@
-# Description
+<!--
+Type of change: Title of the PR should clearly mention which type of PR is this, you can select any of the below mentioned types:
 
-Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
+- docs - The PR contains Documentation ONLY changes. 
+- feat - The PR contains new feature/enhancements.
+- fix - The PR contains a bug fix.
+- chore - Development changes related to the build system (involving scripts, configurations or tools) and package dependencies.
+- test - Development changes related to tests.
+- perf - Changes related to performance improvements.
 
-Fixes # (issue)
+Example Title: 
+docs: Webhook CI documentation changes
+-->
 
-## Type of change
+# Description
+<!--
+Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
+-->
 
-- [ ] Bug fix (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)
-- [ ] This change requires a documentation update
+Fixes #
 
-# How Has This Been Tested?
+## How Has This Been Tested?
 Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
-
+<!--test-cases
 - [ ] Test case A
 - [ ] Test case B
+-->
 
-
-# Checklist:
+## Checklist:
 
 * [ ] The title of the PR states what changed and the related issues number (used for the release note).
-* [ ] Does this PR require documentation updates?
+* [ ] Does this PR requires documentation updates?
 * [ ] I've updated documentation as required by this PR.
-* [ ] I have performed a self-review of my own code
-* [ ] I have commented my code, particularly in hard-to-understand areas
-* [ ] I have tested it for all user roles
-* [ ] I have added all the required unit/api test cases
+* [ ] I have performed a self-review of my own code.
+* [ ] I have commented my code, particularly in hard-to-understand areas.
+* [ ] I have tested it for all user roles.
+* [ ] I have added all the required unit/api test cases.
+
+## Does this PR introduce a user-facing change?
+<!--
+If NO, leave the release-note block blank.
+If YES, a release note is required:
+Enter your extended release note in the block below. If the PR requires additional manual action from users switching to the new version, include the string "action-required".
 
+-->
+```release-note
 
+```