Update config.yml

[neeru24]

I’ve fixed:

• Placeholder URLs

• Clearer descriptions

• Consistent emoji usage

• Proper GitHub issue-template config 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 refines the repository's issue template configuration by updating contact links to point to the correct repository, enhancing their descriptions for clarity, and adding a dedicated link for feature requests. These changes aim to improve the user experience when seeking support or contributing ideas.

Highlights

• Updated Contact Links: The placeholder URLs for GitHub Discussions and Documentation have been updated to point to the correct repository: 'NexGenStudioDev/LocalMind'.
• Enhanced Descriptions: The 'about' descriptions for the existing contact links have been made clearer and more detailed, providing better guidance to users.
• New Feature Request Link: A new contact link for 'Feature Requests' has been added, directing users to a specific 'ideas' category within GitHub Discussions.

🧠 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 updates the contact links in the issue template configuration, replacing placeholder URLs and adding more descriptive text. A new link for feature requests has also been added. These changes are a good improvement for guiding contributors. However, there appears to be a critical issue with the file path: .github/ ISSUE_TEMPLATE/config.yml. The space in the ISSUE_TEMPLATE directory name will likely prevent GitHub from loading this configuration. To fix this, the directory should be renamed from ISSUE_TEMPLATE to ISSUE_TEMPLATE.