chore: update issue template and add conversion workflow

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,7 +1,7 @@
 name: '🐞 Bug report'
 description: Create a report to help us improve, Ask questions in Discussions / 创建一个问题报告以帮助我们改进，提问请到 Discussions
 title: '[Bug]: '
-labels: ['bug']
+labels: ['status: waiting for maintainer']
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/docs-feedback.yml

@@ -0,0 +1,33 @@
+name: 'Docs feedback'
+description: Improve documentation about AntV G6.
+labels: ['status: waiting for maintainer', 'docs-feedback']
+title: '[docs] '
+body:
+  - type: input
+    id: page-url
+    attributes:
+      label: Related page
+      description: Which page of the documentation is this about?
+      placeholder: https://g6.antv.antgroup.com/
+    validations:
+      required: true
+  - type: dropdown
+    attributes:
+      label: Kind of issue
+      description: What kind of problem are you facing?
+      options:
+        - Unclear explanations
+        - Missing information
+        - Broken demo
+        - Other
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Issue description
+      description: |
+        Let us know what went wrong when you were using this documentation and what we could do to improve it.
+  - type: textarea
+    attributes:
+      label: Context
+      description: What are you trying to accomplish? Providing context helps us come up with a solution that is more useful in the real world.

.github/ISSUE_TEMPLATE/feature.yml

@@ -1,9 +1,8 @@
 name: '💡 Feature Request'
 description: I have a suggestion (and may want to implement it) / 我有一个建议（或者想参与贡献）
 title: '[Feat]: '
-labels: ['feature']
+labels: ['status: waiting for maintainer']
 body:
-
   - type: textarea
     id: description
     attributes:
@@ -19,4 +18,4 @@ body:
         - ✅ Yes / 是
         - ❌ No / 否
     validations:
-      required: true
+      required: true

.github/workflows/no-response.yml

@@ -0,0 +1,36 @@
+name: No response
+
+# `issues`.`closed`, `issue_comment`.`created`, and `scheduled` event types are required for this Action
+# to work properly.
+on:
+  issues:
+    types: [closed]
+  issue_comment:
+    types: [created]
+  schedule:
+    # These runs in our repos are spread evenly throughout the day to avoid hitting rate limits.
+    # If you change this schedule, consider changing the remaining repositories as well.
+    # Runs at 12 am, 12 pm
+    - cron: '0 0,12 * * *'
+
+permissions: {}
+
+jobs:
+  noResponse:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      issues: write
+    steps:
+      - uses: MBilalShafi/no-response-add-label@8336c12292902f27b931154c34ba4670cb9899a2
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          # Number of days of inactivity before an Issue is closed for lack of response
+          daysUntilClose: 7
+          # Label requiring a response
+          responseRequiredLabel: 'status: waiting for author'
+          # Label to add back when required label is removed
+          optionalFollowupLabel: 'status: waiting for maintainer'
+          # Comment to post when closing an Issue for lack of response. Set to `false` to disable
+          closeComment: >
+            Since the issue is missing key information and has been inactive for 7 days, it has been automatically closed. If you wish to see the issue reopened, please provide the missing information.