Docs: Add Contributing Guidelines and Code of Conduct

[mdxabu]

Added Community guidelines:

• Added a CODE_OF_CONDUCT.md file outlining standards for respectful and inclusive behavior, unacceptable conduct, responsibilities of maintainers, scope of application, enforcement procedures, and attribution to the Contributor Covenant.

[gemini-code-assist]

Summary of Changes

Hello @mdxabu, 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 foundational documentation to guide and govern community interactions and contributions to the BHV project. By adding a Code of Conduct and detailed Contributing Guidelines, the project aims to cultivate a welcoming, inclusive, and efficient environment for all contributors, ensuring clarity on expectations and processes for participation.

Highlights

• Code of Conduct Added: A new CODE_OF_CONDUCT.md file has been introduced, establishing clear guidelines for respectful and inclusive behavior within the project community. This document outlines pledges, standards of acceptable and unacceptable conduct, maintainer responsibilities, scope of application, and enforcement procedures, adapted from the Contributor Covenant.
• Comprehensive Contributing Guidelines: A detailed CONTRIBUTING.md file has been added to guide new and existing contributors. It covers essential aspects such as setting up the development environment, various types of contributions, the development workflow, guidelines for creating issues and pull requests (including templates and conventional commit formats), code style, documentation practices, community interaction, and security vulnerability reporting.

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 adds important community health files: a Code of Conduct and Contributing Guidelines. This is a great step for the project! The documents are comprehensive and well-structured. I've provided some feedback to improve clarity, fix formatting issues, and ensure the instructions for contributors are accurate and easy to follow. Key suggestions include correcting the git workflow instructions, clarifying technical choices like the database, and fixing some markdown formatting.

[gemini-code-assist]

There's a formatting issue with the markdown code blocks in this section. The Feature Request Template code block starting on line 185 is not closed, which causes the subsequent sections (Documentation Issue Template, Other Issue Types, Issue Labels) to be rendered as part of the code block. The stray ```` on line 227 seems misplaced.

To fix this, you should:

1. Add closing backticks (```) after line 199 to close the feature request template.
2. Remove the stray backticks on line 227.

[gemini-code-assist]

This section provides conflicting information about the database. It first states to Use MongoDB for Database. and then suggests Using Github Repo as a Database(Idea). This can be very confusing for new contributors. Please clarify which database technology is in use or intended to be used for the project.

[gemini-code-assist]

The file is missing a final newline character. It's a common convention to end files with a newline to avoid issues with some tools and to follow POSIX standards.

Suggested change

	This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html.
	This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html.

[gemini-code-assist]

This line mentions a CONTRIBUTORS.md file, but this file does not exist in the repository. To avoid confusion, you should either create this file or remove this line from the recognition section.