更新issue模板

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -32,7 +32,7 @@ body:
     id: system-info
     attributes:
       label: System Info
-      description: Output of `npx envinfo --system --npmPackages vue --binaries --browsers`
+      description: Output of `npx envinfo --system --binaries --browsers`
       render: shell
       placeholder: System, Binaries, Browsers
   - type: textarea

.github/ISSUE_TEMPLATE/config.yml

@@ -2,7 +2,7 @@ blank_issues_enabled: false
 contact_links:
   - name: Telegram Chat
     url: https://t.me/jiao_long
-    about: Ask questions and discuss with other Vue users in real time.
+    about: Ask questions and discuss with other Qinglong users in real time.
   - name: Questions & Discussions
     url: https://github.com/whyour/qinglong/discussions/new?category=q-a
     about: Use GitHub discussions for message-board style questions and discussions.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -2,23 +2,39 @@ name: "\U0001F680 New feature proposal"
 description: Suggest an idea for this project
 labels: [":sparkles: feature request"]
 body:
-  - type: textarea
+  - type: markdown
-    id: problem-description
     attributes:
-      label: What problem does this feature solve?
+      value: |
-      description: |
+        Thanks for your interest in the project and taking the time to fill out this feature report!
-        Explain your use case, context, and rationale behind this feature request. More importantly, what is the **end user experience** you are trying to build that led to the need for this feature?
+  - type: textarea
-
+    id: feature-description
-        An important design goal of Vue is keeping the API surface small and straightforward. In general, we only consider adding new features that solve a problem that cannot be easily dealt with using existing APIs (i.e. not just an alternative way of doing things that can already be done). The problem should also be common enough to justify the addition.
+    attributes:
-      placeholder: Problem description
+      label: Clear and concise description of the problem
+      description: "Explain your use case, context, and rationale behind this feature request. More importantly, what is the **end user experience** you are trying to build that led to the need for this feature?"
     validations:
       required: true
   - type: textarea
-    id: proposed-API
+    id: suggested-solution
     attributes:
-      label: What does the proposed API look like?
+      label: Suggested solution
-      description: |
+      description: "In module [xy] we could provide following implementation..."
-        Describe how you propose to solve the problem and provide code samples of how the API would work once implemented. Note that you can use [Markdown](https://guides.github.com/features/mastering-markdown/) to format your code blocks.
-      placeholder: Steps to reproduce
     validations:
       required: true
+  - type: textarea
+    id: alternative
+    attributes:
+      label: Alternative
+      description: Clear and concise description of any alternative solutions or features you've considered.
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional context
+      description: Any other context or screenshots about the feature request here.
+  - type: checkboxes
+    id: checkboxes
+    attributes:
+      label: Validations
+      description: Before submitting the issue, please make sure you do the following
+      options:
+        - label: Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
+          required: true