mooncake/.github/ISSUE_TEMPLATE · openFuyao/mooncake - AtomGit

GGitHubchore(issue): Fix typo in issue template (#858 )

dfd445ac创建于 2025年9月18日历史提交

文件	最后提交记录	最后更新时间
1.bug_report.yml	[Misc] Add Issue Template in Github (#506) * [Misc] Add Issue Template in Github Based on the [github issue template tutorial](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository) and the taxonomy of the [vllm issue template](https://github.com/vllm-project/vllm/tree/main/.github/ISSUE_TEMPLATE), I exported and labeled the open issues of the mooncake community, see [this table](https://airtable.com/appbJ0k8FJwYl46bK/shrMGqLcypyY4Wjjb), and got the following issue classification: `shell . ├── 1.bug_report.yml ├── 2.usage.yml ├── 3.performance_dicussion.yml ├── 4.feature_request.yml ├── 5.RFC.yml ├── 6.documentation.yml ├── 7.installation.yml └── config.yaml` * Modify the issue template based on feedback Simplify the content and use a blank template by default	1 年前
2.usage.yml	[Misc] Add Issue Template in Github (#506) * [Misc] Add Issue Template in Github Based on the [github issue template tutorial](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository) and the taxonomy of the [vllm issue template](https://github.com/vllm-project/vllm/tree/main/.github/ISSUE_TEMPLATE), I exported and labeled the open issues of the mooncake community, see [this table](https://airtable.com/appbJ0k8FJwYl46bK/shrMGqLcypyY4Wjjb), and got the following issue classification: `shell . ├── 1.bug_report.yml ├── 2.usage.yml ├── 3.performance_dicussion.yml ├── 4.feature_request.yml ├── 5.RFC.yml ├── 6.documentation.yml ├── 7.installation.yml └── config.yaml` * Modify the issue template based on feedback Simplify the content and use a blank template by default	1 年前
3.performance_dicussion.yml	chore(issue): Fix typo in issue template (#858)	9 个月前
4.feature_request.yml	[Misc] Add Issue Template in Github (#506) * [Misc] Add Issue Template in Github Based on the [github issue template tutorial](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository) and the taxonomy of the [vllm issue template](https://github.com/vllm-project/vllm/tree/main/.github/ISSUE_TEMPLATE), I exported and labeled the open issues of the mooncake community, see [this table](https://airtable.com/appbJ0k8FJwYl46bK/shrMGqLcypyY4Wjjb), and got the following issue classification: `shell . ├── 1.bug_report.yml ├── 2.usage.yml ├── 3.performance_dicussion.yml ├── 4.feature_request.yml ├── 5.RFC.yml ├── 6.documentation.yml ├── 7.installation.yml └── config.yaml` * Modify the issue template based on feedback Simplify the content and use a blank template by default	1 年前
5.RFC.yml	[Misc] Add Issue Template in Github (#506) * [Misc] Add Issue Template in Github Based on the [github issue template tutorial](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository) and the taxonomy of the [vllm issue template](https://github.com/vllm-project/vllm/tree/main/.github/ISSUE_TEMPLATE), I exported and labeled the open issues of the mooncake community, see [this table](https://airtable.com/appbJ0k8FJwYl46bK/shrMGqLcypyY4Wjjb), and got the following issue classification: `shell . ├── 1.bug_report.yml ├── 2.usage.yml ├── 3.performance_dicussion.yml ├── 4.feature_request.yml ├── 5.RFC.yml ├── 6.documentation.yml ├── 7.installation.yml └── config.yaml` * Modify the issue template based on feedback Simplify the content and use a blank template by default	1 年前
6.documentation.yml	[Misc] Add Issue Template in Github (#506) * [Misc] Add Issue Template in Github Based on the [github issue template tutorial](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository) and the taxonomy of the [vllm issue template](https://github.com/vllm-project/vllm/tree/main/.github/ISSUE_TEMPLATE), I exported and labeled the open issues of the mooncake community, see [this table](https://airtable.com/appbJ0k8FJwYl46bK/shrMGqLcypyY4Wjjb), and got the following issue classification: `shell . ├── 1.bug_report.yml ├── 2.usage.yml ├── 3.performance_dicussion.yml ├── 4.feature_request.yml ├── 5.RFC.yml ├── 6.documentation.yml ├── 7.installation.yml └── config.yaml` * Modify the issue template based on feedback Simplify the content and use a blank template by default	1 年前
7.installation.yml	[Misc] Add Issue Template in Github (#506) * [Misc] Add Issue Template in Github Based on the [github issue template tutorial](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository) and the taxonomy of the [vllm issue template](https://github.com/vllm-project/vllm/tree/main/.github/ISSUE_TEMPLATE), I exported and labeled the open issues of the mooncake community, see [this table](https://airtable.com/appbJ0k8FJwYl46bK/shrMGqLcypyY4Wjjb), and got the following issue classification: `shell . ├── 1.bug_report.yml ├── 2.usage.yml ├── 3.performance_dicussion.yml ├── 4.feature_request.yml ├── 5.RFC.yml ├── 6.documentation.yml ├── 7.installation.yml └── config.yaml` * Modify the issue template based on feedback Simplify the content and use a blank template by default	1 年前
config.yaml	[Misc] Add Issue Template in Github (#506) * [Misc] Add Issue Template in Github Based on the [github issue template tutorial](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository) and the taxonomy of the [vllm issue template](https://github.com/vllm-project/vllm/tree/main/.github/ISSUE_TEMPLATE), I exported and labeled the open issues of the mooncake community, see [this table](https://airtable.com/appbJ0k8FJwYl46bK/shrMGqLcypyY4Wjjb), and got the following issue classification: `shell . ├── 1.bug_report.yml ├── 2.usage.yml ├── 3.performance_dicussion.yml ├── 4.feature_request.yml ├── 5.RFC.yml ├── 6.documentation.yml ├── 7.installation.yml └── config.yaml` * Modify the issue template based on feedback Simplify the content and use a blank template by default	1 年前