9 hacktoberfest eligibility

[sanjaysah101]

What changes have been made?

[Provide a short description of the changes.]

Related Issues or Tasks

#28

Checklist

• Code has been linted.
• Tests have been added (if applicable).
• Code has been formatted with Prettier.
• Documentation has been updated (if applicable).

[gemini-code-assist]

Summary of Changes

Hello @sanjaysah101, 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 improves the project's contribution experience by introducing structured issue and pull request templates. These changes aim to streamline the process for reporting bugs, requesting features, and submitting code, making it easier for contributors to provide necessary information and for maintainers to process submissions. Additionally, it includes minor updates to other project documentation and configuration files to reflect the project's current state and branding.

Highlights

• Standardized Contribution Templates: Replaced old, generic issue and pull request templates with new, structured YAML-based issue templates (for bug reports and feature requests) and specific Markdown-based pull request templates (for bug fixes, features, and refactors). This includes a main PR template to guide contributors to the appropriate specific template.
• Documentation Enhancements: Updated the CONTRIBUTING.md file to remove a broken link, generalize git clone examples with placeholders, and correct command indentations. The CODE_OF_CONDUCT.md was also updated to include a direct mailto link for reporting issues.
• License and Configuration Updates: The LICENSE file's copyright year was updated from 2014 to 2025, and the copyright holder was changed to 'Ansopedia'. A missing newline character was also added. Additionally, the .vscode/settings.json file was updated to include 'Ansopedia' in the cSpell dictionary.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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 issue and pull request templates, and refines the CONTRIBUTING.md guide, enhancing the project's contribution workflow. I suggest making key fields mandatory in the issue templates and improving consistency in the contribution guide. Also, the copyright year in the LICENSE file should be updated.