Update issue templates

[Dargon789]

Summary by Sourcery

Add standardized GitHub issue templates to guide users when filing bugs, feature requests, or other custom issues.

Documentation:

• Introduce a structured bug report template capturing environment details and reproduction steps.
• Introduce a structured feature request template capturing problem, proposed solution, and alternatives.
• Add a generic custom issue template for miscellaneous reports.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
legion	Ready	Preview, Comment	Apr 20, 2026 1:24am

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[sourcery-ai]

Reviewer's Guide

Adds structured GitHub issue templates for bug reports, feature requests, and a generic custom issue type to standardize incoming issues.

Flow diagram for GitHub issue template selection

flowchart TD
  A[Open repository Issues tab] --> B[Click New issue]
  B --> C[GitHub shows issue_template chooser]
  C --> D[Bug_report_template]
  C --> E[Feature_request_template]
  C --> F[Custom_issue_template]

  D --> D1[Fill bug description]
  D1 --> D2[Add reproduction steps]
  D2 --> D3[Specify expected behavior]
  D3 --> D4[Attach screenshots]
  D4 --> D5[Provide desktop and smartphone environment]
  D5 --> G[Submit issue]

  E --> E1[Describe problem context]
  E1 --> E2[Describe desired solution]
  E2 --> E3[List alternative solutions]
  E3 --> E4[Add additional context or screenshots]
  E4 --> G

  F --> F1[Describe custom issue purpose]
  F1 --> F2[Add relevant details]
  F2 --> G

  G[Issue created with structured template content] --> H[Repository maintainers triage issue]

Loading

File-Level Changes

Change	Details	Files
Introduce a structured bug report issue template using GitHub’s issue forms markdown.	Create a bug report template with front-matter metadata (name, about, title, labels, assignees). Add structured sections for description, reproduction steps, expected behavior, screenshots, desktop environment, mobile environment, and additional context.	.github/ISSUE_TEMPLATE/bug_report.md
Introduce a structured feature request issue template.	Create a feature request template with front-matter metadata (name, about, title, labels, assignees). Add sections to capture problem description, desired solution, considered alternatives, and additional context/screenshots.	.github/ISSUE_TEMPLATE/feature_request.md
Add a generic custom issue template stub.	Create a minimal custom issue template with front-matter metadata (name, about, title, labels, assignees). Leave the body empty for future customization.	.github/ISSUE_TEMPLATE/custom.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• Consider either removing the custom.md template or filling in a more specific about and body so contributors understand when to use it versus the bug/feature templates.
• You might want to pre-populate the labels fields (e.g., bug, enhancement) so that issues created from these templates are automatically categorized.
• To reduce noise for non-relevant platforms, consider combining the desktop and smartphone environment sections into a single "Environment" section with optional fields (OS, browser, device) instead of two separate blocks.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider either removing the `custom.md` template or filling in a more specific `about` and body so contributors understand when to use it versus the bug/feature templates.
- You might want to pre-populate the `labels` fields (e.g., `bug`, `enhancement`) so that issues created from these templates are automatically categorized.
- To reduce noise for non-relevant platforms, consider combining the desktop and smartphone environment sections into a single "Environment" section with optional fields (OS, browser, device) instead of two separate blocks.

## Individual Comments

### Comment 1
<location path=".github/ISSUE_TEMPLATE/feature_request.md" line_range="11" />
<code_context>
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
</code_context>
<issue_to_address>
**suggestion (typo):** Use the more appropriate abbreviation "E.g.," instead of "Ex."

Here, `e.g.,` ("for example") is the standard and grammatically correct form. Please update the sentence accordingly.

```suggestion
A clear and concise description of what the problem is. E.g., I'm always frustrated when [...]
```
</issue_to_address>

Fix all in Cursor

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request adds GitHub issue templates for bug reports, feature requests, and custom issues. Feedback focuses on correcting the OS example for desktops, ensuring consistent formatting with colons in the bug report template, and adding a placeholder to the custom issue template.