Update issue templates

[wizenink]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @wizenink, 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 introduces standardized issue templates for bug reports and feature requests. The primary goal is to enhance the quality and consistency of issue submissions by providing clear, predefined structures for community members to follow when reporting problems or suggesting new features. This will help maintainers gather necessary information more efficiently and streamline the issue management process.

Highlights

• New Bug Report Template: A new issue template for bug reports has been added, providing structured fields for describing bugs, reproduction steps, expected behavior, and system information.
• New Feature Request Template: A new issue template for feature requests has been added, guiding users to describe problems, desired solutions, and alternative considerations.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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 new issue templates for bug reports and feature requests. The templates are well-structured, but I've suggested a few improvements to make them even more effective. For both templates, I've recommended automatically adding labels to help with issue triaging. For the bug report, I've suggested collecting more environment details, such as the software version, which is crucial for reproducibility. For the feature request, I've suggested pre-filling the title to encourage a consistent format.

[gemini-code-assist]

To help with triaging, it's a good practice to automatically assign a bug label to issues created from this template. This will help filter and manage bug reports more efficiently.

Suggested change

	labels: ''
	labels: 'bug'

[gemini-code-assist]

To gather more comprehensive information for debugging, it's better to request more environment details. Renaming 'Desktop' to 'Environment' is more generic, and adding a field for the software version is crucial for reproducing bugs. I've also added a missing colon to Architecture for consistency.

Suggested change

	**Desktop (please complete the following information):**
	- OS: [e.g. Linux]
	- Architecture [e.g x86_64]
	**Environment (please complete the following information):**
	- OS: [e.g. Linux]
	- Architecture: [e.g. x86_64]
	- Software Version: [e.g. v1.0.0]

[gemini-code-assist]

To help categorize new feature requests and maintain a consistent format for issue titles, you could prefix the title with feat: . This is a common convention that aligns with practices like Conventional Commits.

Suggested change

	title: ''
	title: 'feat: '

[gemini-code-assist]

It's helpful to automatically add a label to feature requests for better organization. The enhancement label is a common choice and helps with filtering and prioritizing work.

Suggested change

	labels: ''
	labels: 'enhancement'