deepseek-ai/DeepGEMM
1
0
Fork 0
mirror of https://github.com/deepseek-ai/DeepGEMM.git synced 2026-11-05 00:47:26 +00:00
Code Issues 162 Projects Packages Wiki Activity

[PR #248] [CLOSED] chore: add GitHub issue templates for bugs, features, and questions #312

New issue
Closed
opened 2026-10-26 21:16:08 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-26 21:16:08 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/deepseek-ai/DeepGEMM/pull/248
Author: @yurekami
Created: 12/25/2025
Status: ❌ Closed

Base: main ← Head: chore/add-issue-templates

📝 Commits (1)

  • 049c3bc chore: add GitHub issue templates

📊 Changes

4 files changed (+204 additions, -0 deletions)

View changed files

➕ .github/ISSUE_TEMPLATE/bug_report.yml (+71 -0)
➕ .github/ISSUE_TEMPLATE/config.yml (+5 -0)
➕ .github/ISSUE_TEMPLATE/feature_request.yml (+69 -0)
➕ .github/ISSUE_TEMPLATE/question.yml (+59 -0)

📄 Description

Summary

Add structured GitHub issue templates to help standardize community contributions and make issue triage easier.

Templates Added

1. Bug Report (bug_report.yml)

  • Description of the bug
  • Steps to reproduce
  • Expected behavior
  • Error message/stack trace
  • Environment details (GPU, CUDA, PyTorch, Python, OS)
  • Additional context

2. Feature Request (feature_request.yml)

  • Problem statement
  • Proposed solution
  • Alternatives considered
  • Feature category (Performance, API, Build, etc.)
  • Use case
  • Contribution willingness checkbox

3. Question (question.yml)

  • Question description
  • Topic category
  • Context/code snippets
  • Optional environment details

4. Config (config.yml)

  • Enables blank issues for edge cases
  • Links to Discussions for community support

Benefits

  • Consistent formatting: All issues follow a standard structure
  • Required fields: Ensures necessary information is provided upfront
  • Automatic labeling: Issues get labeled (bug, enhancement, question)
  • Easier triage: Maintainers can quickly understand and prioritize issues
  • Better community experience: Contributors know what information to provide

Preview

When users create a new issue, they'll see a template chooser:

  • Bug Report
  • Feature Request
  • Question
  • Open a blank issue

🤖 Generated with Claude Code

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/deepseek-ai/DeepGEMM/pull/248 **Author:** [@yurekami](https://github.com/yurekami) **Created:** 12/25/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `chore/add-issue-templates` --- ### 📝 Commits (1) - [`049c3bc`](https://github.com/deepseek-ai/DeepGEMM/commit/049c3bc2a384e6f6eff535cef654d5da7f23d73a) chore: add GitHub issue templates ### 📊 Changes **4 files changed** (+204 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.github/ISSUE_TEMPLATE/bug_report.yml` (+71 -0) ➕ `.github/ISSUE_TEMPLATE/config.yml` (+5 -0) ➕ `.github/ISSUE_TEMPLATE/feature_request.yml` (+69 -0) ➕ `.github/ISSUE_TEMPLATE/question.yml` (+59 -0) </details> ### 📄 Description ## Summary Add structured GitHub issue templates to help standardize community contributions and make issue triage easier. ## Templates Added ### 1. Bug Report (`bug_report.yml`) - Description of the bug - Steps to reproduce - Expected behavior - Error message/stack trace - Environment details (GPU, CUDA, PyTorch, Python, OS) - Additional context ### 2. Feature Request (`feature_request.yml`) - Problem statement - Proposed solution - Alternatives considered - Feature category (Performance, API, Build, etc.) - Use case - Contribution willingness checkbox ### 3. Question (`question.yml`) - Question description - Topic category - Context/code snippets - Optional environment details ### 4. Config (`config.yml`) - Enables blank issues for edge cases - Links to Discussions for community support ## Benefits - **Consistent formatting**: All issues follow a standard structure - **Required fields**: Ensures necessary information is provided upfront - **Automatic labeling**: Issues get labeled (`bug`, `enhancement`, `question`) - **Easier triage**: Maintainers can quickly understand and prioritize issues - **Better community experience**: Contributors know what information to provide ## Preview When users create a new issue, they'll see a template chooser: - Bug Report - Feature Request - Question - Open a blank issue 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-26 21:16:08 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
public-sync-20261014
0930-release
nv_dev
fix-mega-moe-fence
public-release-2609
public-release-2607
public-release-2606
mega-update
public-release-260416
ko3n1g/ci/build-wheels
nv_dev_f8e8fb5
nv_dev_950d31a
nv_dev_67fc648
nv_dev_c491439
nv_dev_4ff3f54
v2.1.1.post3
v2.1.1.post2
v2.1.1.post1
v2.1.1
v2.1.0
Labels
Clear labels   
pull-request
Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/DeepGEMM#312
No description provided.