Update feature_request.yml

[neeru24]

I’ve enforced better structure, clearer wording, and mandatory fields where it matters

@abhishek-nexgen-dev fixes #133

[github-actions]

Thanks for creating a PR for your Issue! ☺️

We'll review it as soon as possible.
In the meantime, please double-check the file changes and ensure that all commits are accurate.

If there are any unresolved review comments, feel free to resolve them. 🙌🏼

[gemini-code-assist]

Summary of Changes

Hello @neeru24, 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 refines the feature request issue template to streamline the submission process and improve the quality of incoming requests. By enforcing a more structured format, clarifying field descriptions, and making key information mandatory, the changes aim to ensure that all necessary details are provided upfront, facilitating better evaluation and management of new features.

Highlights

• Improved Template Structure: The feature request issue template has been updated with clearer field IDs and enhanced introductory text to guide users more effectively.
• Mandatory Fields Enforced: The 'Alternatives Considered' and 'Additional Context' fields are now mandatory, ensuring that submitters provide comprehensive information.
• Enhanced Priority Options: A 'Critical' option has been added to the 'Priority' dropdown, allowing for more granular classification of feature importance.
• New Confirmation Step: A mandatory checkbox has been introduced, requiring users to confirm they have searched existing issues before submitting a new feature request.
• Visual Enhancements: Emojis have been added to the labels of several fields to improve readability and user experience.

🧠 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.

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 significantly improves the feature request template by enforcing a better structure, adding clearer wording with helpful icons and placeholders, and making key fields mandatory. The addition of a confirmation checkbox to prevent duplicate requests is also a valuable improvement. My only suggestion is to reconsider making the 'Additional Context' field mandatory, as it may not always be applicable for every feature request. Overall, these changes will lead to higher quality feature submissions.

[gemini-code-assist]

While making most fields required improves the quality of feature requests, making additional_context mandatory might be overly strict. Users may not always have mockups, screenshots, or other context to add, especially for straightforward feature requests. Forcing them to fill this field could lead to them simply entering 'N/A' or similar, which doesn't add value. Consider making this field optional to improve the user experience when submitting a feature request.

      required: false