Clean up issue templates

This

.github/ISSUE_TEMPLATE/bug-report.md → .github/ISSUE_TEMPLATE/00-bug-report.md

@@ -1,14 +1,11 @@
 ---
 name: "\U0001F41B Bug report"
 about: To help the developer act on the issues, please include a description of your environment, preferably a minimum script to reproduce the problem.
-title: "[Bug] "
-labels: "type: bug"
-
+title: ""
+labels: bug
 ---
 
-Thanks for participating in the TVM community! We use https://discuss.tvm.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking.  You are always welcomed to post on the forum first :smile_cat:
-
-Issues that are inactive for a period of time may get closed. We adopt this policy so that we won't lose track of actionable issues that may fall at the bottom of the pile. Feel free to reopen a new one if you feel there is an additional problem that needs attention when an old one gets closed.
+Thanks for participating in the TVM community! We use https://discuss.tvm.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking. You are always welcomed to post on the forum first :smile_cat:
 
 ### Expected behavior
 

.github/ISSUE_TEMPLATE/01-documentation.md

@@ -0,0 +1,21 @@
+---
+name: "\U0001F4C4 Documentation"
+about: Use this template to suggest additions and changes to the documentation.
+title: ""
+labels: doc
+---
+
+Thanks for participating in the TVM community! We use https://discuss.tvm.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking. You are always welcomed to post on the forum first :smile_cat:
+
+### Documentation Link
+
+Include a link to the relevant documentation page and details about the section in question. For example:
+
+- https://tvm.apache.org/docs/tutorial/install.html#sphx-glr-tutorial-install-py
+- https://github.com/apache/tvm/blob/main/docs/install/nnpack.rst?plain=1#L35-L44
+
+### Additions/Changes Requested
+
+If an RFC/discuss post exists, link it here.
+
+Otherwise, specify what actions should be taken to provide additional clarity/readability/reproducibility to the document. Include code snippets from the previous documentation if applicable.

.github/ISSUE_TEMPLATE/02-feature-request.md

@@ -0,0 +1,19 @@
+---
+name: "\U0001F680 Feature Request"
+about: "Describe a feature you would like to see supported in TVM"
+title: ""
+labels: feature-request
+---
+
+Thanks for participating in the TVM community! We use https://discuss.tvm.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking. You are always welcomed to post on the forum first :smile_cat:
+
+### Feature and Motivation
+
+- Describe the feature
+- Describe any API changes
+- What benefits this feature will have
+
+### Alternatives and Other Context
+
+- Are you willing to contribute to this feature? (yes / no)
+- Any other information

.github/ISSUE_TEMPLATE/feature-tracking.md → .github/ISSUE_TEMPLATE/03-feature-tracking.md

@@ -1,14 +1,14 @@
 ---
-name: "\U0001F527 Feature Tracking"
-about: List clear, small actionable items so we can track the progress of the change.
-title: "[Tracking Issue] "
-labels: type:rfc-tracking
-
+name: "\U0001F527 RFC Feature Tracking"
+about: List clear, small actionable items so we can track the progress of a change
+title: ""
+labels: rfc-tracking
 ---
 
-Thanks for participating in the TVM community! We use https://discuss.tvm.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking.  You are always welcomed to post on the forum first :smile_cat:
+Thanks for participating in the TVM community! We use https://discuss.tvm.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking. You are always welcomed to post on the forum first :smile_cat:
 
 Issues that are inactive for a period of time may get closed. We adopt this policy so that we won't lose track of actionable issues that may fall at the bottom of the pile. Feel free to reopen a new one if you feel there is an additional problem that needs attention when an old one gets closed.
 
 ### This issue is to track progress for FEATURE NAME
+
 - [ ] P1. Title of this piece of the feature (PR link if available)

.github/ISSUE_TEMPLATE/flaky-test.md → .github/ISSUE_TEMPLATE/04-flaky-test.md

@@ -1,13 +1,13 @@
 ---
 name: "\U00002744 Flaky Test"
-about: Report a flaky test, make sure to include links to CI runs, a sample failure log, and the name of the test(s)
-title: "[Flaky Test] "
-labels: "test: flaky"
+about: Report a flaky test or general CI problem, make sure to include links to CI runs, a sample failure log, and the name of the test(s)
+title: ""
+labels: flaky-test, ci
 ---
 
 Thanks for participating in the TVM community! We use https://discuss.tvm.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking. You are always welcomed to post on the forum first :smile_cat:
 
-These tests were found to be flaky (intermittently failing on `main` or failed in a PR with unrelated changes). As per [the docs](https://github.com/apache/tvm/blob/main/docs/contribute/ci.rst#handling-flaky-failures, these failures will be disabled in a PR that references this issue until the test owners can fix the source of the flakiness.
+These tests were found to be flaky (intermittently failing on `main` or failed in a PR with unrelated changes). As per [the docs](https://github.com/apache/tvm/blob/main/docs/contribute/ci.rst#handling-flaky-failures), these failures will be disabled in a PR that references this issue until the test owners can fix the source of the flakiness.
 
 ### Test(s)
 

.github/ISSUE_TEMPLATE/ci-image.md → .github/ISSUE_TEMPLATE/05-ci-image.md

@@ -1,13 +1,11 @@
 ---
 name: "\U0001F40B Update CI Docker Image"
 about: Provide information on CI Docker Images requiring updates
-title: "[CI Image] "
-
+title: ""
+labels: docker-update, ci
 ---
 
-Thanks for participating in the TVM community! We use https://discuss.tvm.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking.  You are always welcomed to post on the forum first :smile_cat:
-
-Issues that are inactive for a period of time may get closed. We adopt this policy so that we won't lose track of actionable issues that may fall at the bottom of the pile. Feel free to reopen a new one if you feel there is an additional problem that needs attention when an old one gets closed.
+Thanks for participating in the TVM community! We use https://discuss.tvm.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking. You are always welcomed to post on the forum first :smile_cat:
 
 - [ ] S0. Reason: For example, a blocked PR or a feature issue
 
@@ -18,6 +16,7 @@ Issues that are inactive for a period of time may get closed. We adopt this poli
 - [ ] S3. Testing the nightly image on ci-docker-staging: https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/ci-docker-staging/...
 
 - [ ] S4. Retag TAG to VERSION:
+
 ```
 docker pull tlcpackstaging/IMAGE_NAME:TAG
 docker tag tlcpackstaging/IMAGE_NAME:TAG tlcpack/IMAGE_NAME:VERSION

.github/ISSUE_TEMPLATE/06-other.md

@@ -0,0 +1,7 @@
+---
+name: "\U00002753 Other"
+about: File an issue that doesn't fit into the other categories
+title: ""
+---
+
+Thanks for participating in the TVM community! We use https://discuss.tvm.ai for any general usage questions and discussions. The issue tracker is used for actionable items such as feature proposals discussion, roadmaps, and bug tracking. You are always welcomed to post on the forum first :smile_cat: