Proposing issue template

[aleozlx]

📌 Description

Summary

• Add GitHub issue form templates (bug report + feature request) to guide reporters through providing component, framework, model, environment,
  and logging info
• Add workflow to auto-apply op: labels based on the component dropdown selection
• Bug report template auto-labels bug + needs-triage; feature request auto-labels feature request + needs-triage
• Blank issues still allowed as fallback

Details

Bug report asks for:

• Component dropdown (Attention, GEMM, MoE, MoE Routing, Comm, Norm, etc.)
• Framework dropdown (vLLM, SGLang, TensorRT-LLM)
• Model name (optional)
• Description, repro steps, environment (GPU, CUDA, driver), and logs
• Includes tips on enabling FLASHINFER_LOGLEVEL for debugging

Feature request asks for:

• Component and framework dropdowns
• Model name and target GPU (optional)
• Description

Issue labeler workflow (issue-labeler.yml):

• Triggers on issue open
• Reads the component dropdown value from the issue body
• Auto-applies the matching op: label (attention, gemm, moe, moe-routing, comm, norm, misc)

🔍 Related Issues

🚀 Pull Request Checklist

Thank you for contributing to FlashInfer! Before we review your pull request, please make sure the following items are complete.

✅ Pre-commit Checks

• I have installed pre-commit by running pip install pre-commit (or used your preferred method).
• I have installed the hooks with pre-commit install.
• I have run the hooks manually with pre-commit run --all-files and fixed any reported issues.

If you are unsure about how to set up pre-commit, see the pre-commit documentation.

🧪 Tests

• Tests have been added or updated as needed.
• All tests are passing (unittest, etc.).

Reviewer Notes

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1e9fa62d-15d2-4df3-8338-000ce1c8b653

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the issue reporting process by introducing structured templates for bug reports and feature requests. These templates aim to streamline the collection of necessary information from users, ensuring that maintainers receive consistent and detailed reports. By guiding reporters through specific fields and automatically applying initial labels, the changes will improve the efficiency of issue triaging and resolution.

Highlights

• Structured Issue Templates: Introduced new GitHub issue form templates for bug reports and feature requests to guide users in providing comprehensive information.
• Detailed Reporting Fields: The templates include dropdowns for component and framework, input fields for model and target GPU, and text areas for description, reproduction steps, environment details, and logs.
• Automated Labeling: Bug reports will be automatically labeled 'bug' and 'needs-triage', while feature requests will receive 'feature request' and 'needs-triage' labels upon creation.
• Blank Issue Fallback: The configuration allows for blank issues to still be created, providing flexibility for reporters.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/issue-labeler.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces GitHub issue templates for bug reports and feature requests, which is a valuable addition for standardizing issue submissions. The templates are well-designed. I've suggested a couple of minor improvements to the bug report template to make the 'Steps to reproduce' and 'Environment' fields mandatory. This change would help ensure that bug reports are consistently high-quality and contain all the necessary information for debugging.

[gemini-code-assist]

To make bug reports more actionable, it's highly recommended to require steps to reproduce. Without a clear reproduction case, it can be very difficult to diagnose and fix bugs. Making this field mandatory will improve the quality of incoming bug reports.

      required: true

[gemini-code-assist]

Environment details are critical for debugging issues in a GPU-accelerated library. Information like GPU model, CUDA version, and driver version is often essential for reproducing bugs. Please consider making this section required to ensure bug reports contain this vital information.

      required: true