fix(docs): move CONTRIBUTING.md from docs/ to repository root

[JacobPEvans-personal]

Summary

• Moves CONTRIBUTING.md from docs/CONTRIBUTING.md to the repository root
• GitHub requires community health files to be at the root (or .github/) to recognise them in the repo profile

Test plan

• Verify GitHub shows the CONTRIBUTING link in the community health section of the repo insights page

[gemini-code-assist]

Summary of Changes

Hello, 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 optimizes the repository structure to improve the visibility of contribution guidelines. By placing the file in the root directory, the project aligns with standard GitHub conventions for community health recognition.

Highlights

• File Relocation: Moved the CONTRIBUTING.md file from the docs/ directory to the repository root.
• Community Health: Ensured that GitHub correctly identifies and displays the contribution guidelines in the repository's community health profile.

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 the 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 counterproductive. 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.

---

A guide for those who wish to aid, At root level now it is displayed. With rules in place for all to see, The project grows in harmony.

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