Updated bug_report.yml

[neeru24]

✅ What’s improved

• All fields are mandatory (including screenshots/logs)

• Clear emojis for better UX

• Added Actual Behavior (very important for debugging)

• Added Browser/App Version

• Added confirmation checkbox to reduce duplicates

• Professional, readable structure

fixes #133
@abhishek-nexgen-dev

[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 significantly enhances the bug reporting process by updating the bug_report.yml issue template. The changes aim to ensure that all submitted bug reports are comprehensive and contain essential information, thereby streamlining the debugging workflow and reducing the effort required to triage and resolve issues. By making key fields mandatory and adding new critical information points, the quality of incoming bug reports is expected to improve substantially.

Highlights

• Mandatory Fields: All fields in the bug report form, including screenshots/logs, are now mandatory to ensure comprehensive issue submissions.
• Enhanced User Experience: Clear emojis have been added to field labels for improved readability and user experience.
• New 'Actual Behavior' Field: A dedicated 'Actual Behavior' field has been introduced and made mandatory, crucial for effective debugging.
• New 'Browser/App Version' Field: A new mandatory field for 'Browser / App Version' has been added to gather environment-specific details.
• Duplicate Reduction: A confirmation checkbox is now required, prompting users to check for existing issues before submission, aiming to reduce duplicates.
• Improved Structure: The overall structure of the bug report template has been refined for a more professional and readable layout.

🧠 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 bug report issue template. The new fields for 'Actual Behavior' and 'Browser/App Version', along with making all fields mandatory, will ensure that maintainers receive all the necessary information to address bugs effectively. The addition of a confirmation checkbox is a great step towards reducing duplicate issues. The overall structure is much clearer and more user-friendly, thanks to the improved descriptions, placeholders, and use of emojis. I have one suggestion to make the 'search for duplicates' step even more effective by including a direct link to the issues page. Overall, this is an excellent contribution to improving the project's contribution workflow.

[gemini-code-assist]

To make it easier for users to search for existing issues, consider adding a direct link to the issues page in this label. This can further help in reducing duplicate bug reports by guiding users to the right place to search.

For example, you could update the label like this (remember to replace OWNER/REPO with your repository's path):

- label: 'I have searched the [existing issues](https://github.com/OWNER/REPO/issues) and this bug has not been reported before.'